github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-27 21:47:07 +00:00
Code Issues Projects Releases Wiki Activity

rewrite all links to prs to k8s links

Browse Source
This commit is contained in:
Mike Danese 2015-08-05 18:09:50 -07:00
parent fe6b15ba2f
commit 8326697055
7 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/admin/cluster-large.md
View File

@ -64,7 +64,7 @@ To avoid running into cloud provider quota issues, when creating a cluster with
### Addon Resources ### Addon Resources
To prevent memory leaks or other resource issues in [cluster addons](../../cluster/addons/) from consuming all the resources available on a node, Kubernetes sets resource limits on addon containers to limit the CPU and Memory resources they can consume (See PR [#10653](https://github.com/GoogleCloudPlatform/kubernetes/pull/10653/files) and [#10778](https://github.com/GoogleCloudPlatform/kubernetes/pull/10778/files)). To prevent memory leaks or other resource issues in [cluster addons](../../cluster/addons/) from consuming all the resources available on a node, Kubernetes sets resource limits on addon containers to limit the CPU and Memory resources they can consume (See PR [#10653](http://pr.k8s.io/10653/files) and [#10778](http://pr.k8s.io/10778/files)).
For example: For example:

2
docs/design/event_compression.md
View File

@ -113,7 +113,7 @@ This demonstrates what would have been 20 separate entries (indicating schedulin
* PR [#4157](http://issue.k8s.io/4157): Add "Update Event" to Kubernetes API * PR [#4157](http://issue.k8s.io/4157): Add "Update Event" to Kubernetes API
* PR [#4206](http://issue.k8s.io/4206): Modify Event struct to allow compressing multiple recurring events in to a single event * PR [#4206](http://issue.k8s.io/4206): Modify Event struct to allow compressing multiple recurring events in to a single event
* PR [#4306](http://issue.k8s.io/4306): Compress recurring events in to a single event to optimize etcd storage * PR [#4306](http://issue.k8s.io/4306): Compress recurring events in to a single event to optimize etcd storage
* PR [#4444](https://github.com/GoogleCloudPlatform/kubernetes/pull/4444): Switch events history to use LRU cache instead of map * PR [#4444](http://pr.k8s.io/4444): Switch events history to use LRU cache instead of map
<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> <!-- BEGIN MUNGE: GENERATED_ANALYTICS -->

4
docs/design/security.md
View File

@ -127,11 +127,11 @@ A pod runs in a *security context* under a *service account* that is defined by
### Related design discussion ### Related design discussion
* [Authorization and authentication](access.md) * [Authorization and authentication](access.md)
* [Secret distribution via files](https://github.com/GoogleCloudPlatform/kubernetes/pull/2030) * [Secret distribution via files](http://pr.k8s.io/2030)
* [Docker secrets](https://github.com/docker/docker/pull/6697) * [Docker secrets](https://github.com/docker/docker/pull/6697)
* [Docker vault](https://github.com/docker/docker/issues/10310) * [Docker vault](https://github.com/docker/docker/issues/10310)
* [Service Accounts:](service_accounts.md) * [Service Accounts:](service_accounts.md)
* [Secret volumes](https://github.com/GoogleCloudPlatform/kubernetes/pull/4126) * [Secret volumes](http://pr.k8s.io/4126)
## Specific Design Points ## Specific Design Points

2
docs/design/security_context.md
View File

@ -192,7 +192,7 @@ It is up to an admission plugin to determine if the security context is acceptab
time of writing, the admission control plugin for security contexts will only allow a context that time of writing, the admission control plugin for security contexts will only allow a context that
has defined capabilities or privileged. Contexts that attempt to define a UID or SELinux options has defined capabilities or privileged. Contexts that attempt to define a UID or SELinux options
will be denied by default. In the future the admission plugin will base this decision upon will be denied by default. In the future the admission plugin will base this decision upon
configurable policies that reside within the [service account](https://github.com/GoogleCloudPlatform/kubernetes/pull/2297). configurable policies that reside within the [service account](http://pr.k8s.io/2297).
<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> <!-- BEGIN MUNGE: GENERATED_ANALYTICS -->

2
hack/cherry_pick_pull.sh
View File

@ -100,7 +100,7 @@ cleanbranch="${NEWBRANCHUNIQ}"
gitamcleanup=true gitamcleanup=true
for pull in "${PULLS[@]}"; do for pull in "${PULLS[@]}"; do
echo "+++ Downloading patch to /tmp/${pull}.patch (in case you need to do this again)" echo "+++ Downloading patch to /tmp/${pull}.patch (in case you need to do this again)"
curl -o "/tmp/${pull}.patch" -sSL "https://github.com/GoogleCloudPlatform/kubernetes/pull/${pull}.patch" curl -o "/tmp/${pull}.patch" -sSL "http://pr.k8s.io/${pull}.patch"
echo echo
echo "+++ About to attempt cherry pick of PR. To reattempt:" echo "+++ About to attempt cherry pick of PR. To reattempt:"
echo " $ git am -3 /tmp/${pull}.patch" echo " $ git am -3 /tmp/${pull}.patch"

2
pkg/apiserver/apiserver_test.go
View File

@ -1943,7 +1943,7 @@ func TestCreateNotFound(t *testing.T) {
handler := handle(map[string]rest.Storage{ handler := handle(map[string]rest.Storage{
"simple": &SimpleRESTStorage{ "simple": &SimpleRESTStorage{
// storage.Create can fail with not found error in theory. // storage.Create can fail with not found error in theory.
// See https://github.com/GoogleCloudPlatform/kubernetes/pull/486#discussion_r15037092. // See http://pr.k8s.io/486#discussion_r15037092.
errors: map[string]error{"create": apierrs.NewNotFound("simple", "id")}, errors: map[string]error{"create": apierrs.NewNotFound("simple", "id")},
}, },
}) })

2
pkg/kubectl/resource/visitor.go
View File

@ -40,7 +40,7 @@ const constSTDINstr string = "STDIN"
// Visitor lets clients walk a list of resources. // Visitor lets clients walk a list of resources.
// TODO: we should rethink how we handle errors in the visit loop // TODO: we should rethink how we handle errors in the visit loop
// (See https://github.com/GoogleCloudPlatform/kubernetes/pull/9357#issuecomment-109600305) // (See http://pr.k8s.io/9357#issuecomment-109600305)
type Visitor interface { type Visitor interface {
Visit(VisitorFunc) error Visit(VisitorFunc) error
} }