whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix kubernetes/community#1010 PR links change (#5546)

Browse Source
This commit is contained in:
Kyle Bai
2017-09-23 00:25:57 +08:00
committed by Steve Perry
parent e7fc8cf845
commit 3d8385e2ca
3 changed files with 6 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/cluster-administration/networking.md
+1 -1
View File
@@ -170,7 +170,7 @@ traffic to the internet.
### Kube-router ### Kube-router
[Kube-router](https://github.com/cloudnativelabs/kube-router) is a purpose-built networking solution for Kubernetes that aims to provide high performance and operational simplicity. Kube-router provides a Linux [LVS/IPVS](http://www.linuxvirtualserver.org/software/ipvs.html)-based service proxy, a Linux kernel forwarding-based pod-to-pod networking solution with no overlays, and iptables/ipset-based network policy enforcer. [Kube-router](https://github.com/cloudnativelabs/kube-router) is a purpose-built networking solution for Kubernetes that aims to provide high performance and operational simplicity. Kube-router provides a Linux [LVS/IPVS](http://www.linuxvirtualserver.org/software/ipvs.html)-based service proxy, a Linux kernel forwarding-based pod-to-pod networking solution with no overlays, and iptables/ipset-based network policy enforcer.
### L2 networks and linux bridging ### L2 networks and linux bridging
docs/tasks/administer-cluster/highly-available-master.md
+1 -2
View File
@@ -154,5 +154,4 @@ To make such deployment secure, communication between etcd instances is authoriz
## Additional reading ## Additional reading
[Automated HA master deployment - design doc](https://git.k8s.io/community/contributors/design-proposals/ha_master.md) [Automated HA master deployment - design doc](https://git.k8s.io/community/contributors/design-proposals/cluster-lifecycle/ha_master.md)
docs/tasks/administer-cluster/namespaces.md
+4 -4
View File
@@ -63,7 +63,7 @@ to define *Hard* resource usage limits that a *Namespace* may consume.
A limit range defines min/max constraints on the amount of resources a single entity can consume in A limit range defines min/max constraints on the amount of resources a single entity can consume in
a *Namespace*. a *Namespace*.
See [Admission control: Limit Range](https://git.k8s.io/community/contributors/design-proposals/admission_control_limit_range.md) See [Admission control: Limit Range](https://git.k8s.io/community/contributors/design-proposals/resource-management/admission_control_limit_range.md)
A namespace can be in one of two phases: A namespace can be in one of two phases:
@@ -236,9 +236,9 @@ Let's create some contents.
```shell ```shell
$ kubectl run snowflake --image=kubernetes/serve_hostname --replicas=2 $ kubectl run snowflake --image=kubernetes/serve_hostname --replicas=2
``` ```
We have just created a deployment whose replica size is 2 that is running the pod called snowflake with a basic container that just serves the hostname. We have just created a deployment whose replica size is 2 that is running the pod called snowflake with a basic container that just serves the hostname.
Note that `kubectl run` creates deployments only on Kubernetes cluster >= v1.2. If you are running older versions, it creates replication controllers instead. Note that `kubectl run` creates deployments only on Kubernetes cluster >= v1.2. If you are running older versions, it creates replication controllers instead.
If you want to obtain the old behavior, use `--generator=run/v1` to create replication controllers. See [`kubectl run`](/docs/user-guide/kubectl/v1.7/#run) for more details. If you want to obtain the old behavior, use `--generator=run/v1` to create replication controllers. See [`kubectl run`](/docs/user-guide/kubectl/v1.7/#run) for more details.
```shell ```shell
$ kubectl get deployment $ kubectl get deployment
@@ -322,7 +322,7 @@ The Namespace provides a unique scope for:
2. delegated management authority to trusted users 2. delegated management authority to trusted users
3. ability to limit community resource consumption 3. ability to limit community resource consumption
Use cases include: Use cases include:
1. As a cluster operator, I want to support multiple user communities on a single cluster. 1. As a cluster operator, I want to support multiple user communities on a single cluster.
2. As a cluster operator, I want to delegate authority to partitions of the cluster to trusted users 2. As a cluster operator, I want to delegate authority to partitions of the cluster to trusted users