From 98a4b521fd8fbf82426354705087ae0a78031cf7 Mon Sep 17 00:00:00 2001 From: Seth Jennings Date: Thu, 20 Oct 2016 10:46:51 -0500 Subject: [PATCH 01/39] AUTOSCALER not AUTOSCALING --- docs/admin/cluster-management.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/admin/cluster-management.md b/docs/admin/cluster-management.md index 7781368bc8..97362c4bab 100644 --- a/docs/admin/cluster-management.md +++ b/docs/admin/cluster-management.md @@ -95,13 +95,13 @@ If you are using GCE then you can either enable it while creating a cluster with To configure cluser autoscaler you have to set 3 environment variables: * `KUBE_ENABLE_CLUSTER_AUTOSCALER` - it enables cluster autoscaler if set to true. -* `KUBE_AUTOSCALING_MIN_NODES` - minimum number of nodes in the cluster. -* `KUBE_AUTOSCALING_MAX_NODES` - maximum number of nodes in the cluster. +* `KUBE_AUTOSCALER_MIN_NODES` - minimum number of nodes in the cluster. +* `KUBE_AUTOSCALER_MAX_NODES` - maximum number of nodes in the cluster. Example: ```shell -KUBE_ENABLE_CLUSTER_AUTOSCALER=true KUBE_AUTOSCALING_MIN_NODES=3 KUBE_AUTOSCALING_MAX_NODES=10 NUM_NODES=5 ./cluster/kube-up.sh +KUBE_ENABLE_CLUSTER_AUTOSCALER=true KUBE_AUTOSCALER_MIN_NODES=3 KUBE_AUTOSCALER_MAX_NODES=10 NUM_NODES=5 ./cluster/kube-up.sh ``` On GKE you configure cluster autoscaler either on cluster creation or update or when creating a particular node pool From 0d3a83f0d51c49be7f05c6afb2df94e9acc17780 Mon Sep 17 00:00:00 2001 From: roopakparikh Date: Fri, 21 Oct 2016 14:01:00 -0700 Subject: [PATCH 02/39] Added Platform9.com solutions at couple of Places Adding Platform9.com Kubernetes solution in the Hosted section as well as Table of solutions. --- docs/getting-started-guides/index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/getting-started-guides/index.md b/docs/getting-started-guides/index.md index a728980e50..b2da179cf9 100644 --- a/docs/getting-started-guides/index.md +++ b/docs/getting-started-guides/index.md @@ -43,6 +43,8 @@ clusters. [KCluster.io](https://kcluster.io) provides highly available and scalable managed Kubernetes clusters for AWS. +[Platform9.com](https://platform9.com/products/kubernetes/) offers managed Kubernetes on-premises or any public cloud, and provides 24/7 health monitoring and alerting. + ### Turn-key Cloud Solutions These solutions allow you to create Kubernetes clusters on a range of Cloud IaaS providers with only a @@ -123,6 +125,7 @@ GKE | | | GCE | [docs](https://clou Stackpoint.io | | multi-support | multi-support | [docs](http://www.stackpointcloud.com) | | Commercial AppsCode.com | Saltstack | Debian | multi-support | [docs](https://appscode.com/products/cloud-deployment/) | | Commercial KCluster.io | | multi-support | multi-support | [docs](https://kcluster.io) | | Commercial +Platform9.com | | multi-support | multi-support | [docs](https://platform9.com/products/kubernetes/) | | Commercial GCE | Saltstack | Debian | GCE | [docs](/docs/getting-started-guides/gce) | ['œ“][1] | Project Azure | CoreOS | CoreOS | Weave | [docs](/docs/getting-started-guides/coreos/azure/) | | Community ([@errordeveloper](https://github.com/errordeveloper), [@squillace](https://github.com/squillace), [@chanezon](https://github.com/chanezon), [@crossorigin](https://github.com/crossorigin)) Azure | Ignition | Ubuntu | Azure | [docs](/docs/getting-started-guides/azure) | | Community (Microsoft: [@brendandburns](https://github.com/brendandburns), [@colemickens](https://github.com/colemickens)) From 115d3cde97ee794bbb7fc073160b17b75df88b31 Mon Sep 17 00:00:00 2001 From: xiangpengzhao Date: Fri, 28 Oct 2016 00:43:49 -0400 Subject: [PATCH 03/39] Fix path in reference.yml --- _data/reference.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_data/reference.yml b/_data/reference.yml index 5d4fe17f7b..62fdb0ca92 100644 --- a/_data/reference.yml +++ b/_data/reference.yml @@ -219,7 +219,7 @@ toc: - title: Replication Controller path: /docs/user-guide/replication-controller/ - title: Resource Quotas - path: /docs/admin/resource-quota/ + path: /docs/admin/resourcequota/ - title: Scheduled Jobs path: /docs/user-guide/scheduled-jobs/ - title: Secrets @@ -269,6 +269,6 @@ toc: - title: Federation Components section: - title: federation-apiserver - path: /docs/admin/federation-apiserver.md + path: /docs/admin/federation-apiserver - title : federation-controller-mananger - path: /docs/admin/federation-controller-manager.md + path: /docs/admin/federation-controller-manager From e34352c152198620da8d135ef5b8aaf19e7dd7ce Mon Sep 17 00:00:00 2001 From: Julien Vey Date: Fri, 28 Oct 2016 10:39:51 +0200 Subject: [PATCH 04/39] Remove line numbers in ingress resource snippet * To be consistent with the rest of the guide. * To simplify copy/paste of the example. --- docs/user-guide/ingress.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/user-guide/ingress.md b/docs/user-guide/ingress.md index 6ce1eb915d..a8324bea24 100644 --- a/docs/user-guide/ingress.md +++ b/docs/user-guide/ingress.md @@ -53,18 +53,18 @@ Make sure you review the [beta limitations](https://github.com/kubernetes/contri A minimal Ingress might look like: ```yaml -01. apiVersion: extensions/v1beta1 -02. kind: Ingress -03. metadata: -04. name: test-ingress -05. spec: -06. rules: -07. - http: -08. paths: -09. - path: /testpath -10. backend: -11. serviceName: test -12. servicePort: 80 +apiVersion: extensions/v1beta1 +kind: Ingress +metadata: + name: test-ingress +spec: + rules: + - http: + paths: + - path: /testpath + backend: + serviceName: test + servicePort: 80 ``` *POSTing this to the API server will have no effect if you have not configured an [Ingress controller](#ingress-controllers).* From f83b95234a70fc8bfec6697c0267b1120203e2be Mon Sep 17 00:00:00 2001 From: Dominic001 Date: Fri, 28 Oct 2016 22:49:17 +0200 Subject: [PATCH 05/39] more explicit etcdctl description assuming that kubernetes is almost always used with docker. In case other container solutions as lxc are integrated this section will need further revision. Just using the bare etcl command is a bit too less, at least there should be a hint that you log in into the container. --- docs/admin/high-availability/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/admin/high-availability/index.md b/docs/admin/high-availability/index.md index efe6ddac4b..62da7f7eb9 100644 --- a/docs/admin/high-availability/index.md +++ b/docs/admin/high-availability/index.md @@ -100,16 +100,16 @@ for `${NODE_IP}` on each machine. #### Validating your cluster -Once you copy this into all three nodes, you should have a clustered etcd set up. You can validate with +Once you copy this into all three nodes, you should have a clustered etcd set up. In case you run your pods on docker container you can validate with ```shell -etcdctl member list +docker exec -i -t < container_id > etcdctl member list ``` and ```shell -etcdctl cluster-health +docker exec -i -t < container_id > etcdctl cluster-health ``` You can also validate that this is working with `etcdctl set foo bar` on one node, and `etcdctl get foo` From f6f0da2f9af5b93e0e31bb286cc9705945df3062 Mon Sep 17 00:00:00 2001 From: Dominic001 Date: Sat, 29 Oct 2016 01:48:34 +0200 Subject: [PATCH 06/39] more generic patch use kubectl exec command so we dont have to worry about container type --- docs/admin/high-availability/index.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/admin/high-availability/index.md b/docs/admin/high-availability/index.md index 62da7f7eb9..ad78270e4a 100644 --- a/docs/admin/high-availability/index.md +++ b/docs/admin/high-availability/index.md @@ -100,16 +100,15 @@ for `${NODE_IP}` on each machine. #### Validating your cluster -Once you copy this into all three nodes, you should have a clustered etcd set up. In case you run your pods on docker container you can validate with - +Once you copy this into all three nodes, you should have a clustered etcd set up. You can validate on master with ```shell -docker exec -i -t < container_id > etcdctl member list +kubectl exec < pod_name > etcdctl member list ``` and ```shell -docker exec -i -t < container_id > etcdctl cluster-health +kubectl exec < pod_name > etcdctl cluster-health ``` You can also validate that this is working with `etcdctl set foo bar` on one node, and `etcdctl get foo` From 68f8244507d3d2de51ac10a8e208df72e6d0330a Mon Sep 17 00:00:00 2001 From: Cao Shufeng Date: Tue, 1 Nov 2016 05:50:43 -0400 Subject: [PATCH 07/39] Add details about loopback cni plugin This change provide a href to users, so that users knowns where to download this loopback cin plugin. And a more accurate link about cni configuration file is provided. --- docs/admin/network-plugins.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/admin/network-plugins.md b/docs/admin/network-plugins.md index 8cfeb658c9..b89ddc88f7 100644 --- a/docs/admin/network-plugins.md +++ b/docs/admin/network-plugins.md @@ -36,11 +36,11 @@ Place plugins in `network-plugin-dir/plugin-name/plugin-name`, i.e if you have a ### CNI -The CNI plugin is selected by passing Kubelet the `--network-plugin=cni` command-line option. Kubelet reads a file from `--cni-conf-dir` (default `/etc/cni/net.d`) and uses the CNI configuration from that file to set up each pod's network. The CNI configuration file must match the [CNI specification](https://github.com/containernetworking/cni/blob/master/SPEC.md), and any required CNI plugins referenced by the configuration must be present in `--cni-bin-dir` (default `/opt/cni/bin`). +The CNI plugin is selected by passing Kubelet the `--network-plugin=cni` command-line option. Kubelet reads a file from `--cni-conf-dir` (default `/etc/cni/net.d`) and uses the CNI configuration from that file to set up each pod's network. The CNI configuration file must match the [CNI specification](https://github.com/containernetworking/cni/blob/master/SPEC.md#network-configuration), and any required CNI plugins referenced by the configuration must be present in `--cni-bin-dir` (default `/opt/cni/bin`). If there are multiple CNI configuration files in the directory, the first one in lexicographic order of file name is used. -In addition to the CNI plugin specified by the configuration file, Kubernetes requires the standard CNI `lo` plugin, at minimum version 0.2.0 +In addition to the CNI plugin specified by the configuration file, Kubernetes requires the standard CNI [`lo`](https://github.com/containernetworking/cni/blob/master/plugins/main/loopback/loopback.go) plugin, at minimum version 0.2.0 ### kubenet @@ -72,4 +72,4 @@ This option is provided to the network-plugin; currently **only kubenet supports * `--network-plugin=exec` specifies that we use the `exec` plugin, with executables located in `--network-plugin-dir`. * `--network-plugin=cni` specifies that we use the `cni` network plugin with actual CNI plugin binaries located in `--cni-bin-dir` (default `/opt/cni/bin`) and CNI plugin configuration located in `--cni-conf-dir` (default `/etc/cni/net.d`). * `--network-plugin=kubenet` specifies that we use the `kubenet` network plugin with CNI `bridge` and `host-local` plugins placed in `/opt/cni/bin` or `network-plugin-dir`. -* `--network-plugin-mtu=9001` specifies the MTU to use, currently only used by the `kubenet` network plugin. \ No newline at end of file +* `--network-plugin-mtu=9001` specifies the MTU to use, currently only used by the `kubenet` network plugin. From c01dcf1a946ba78eb233c1e59f102cfc093f0df7 Mon Sep 17 00:00:00 2001 From: deads2k Date: Tue, 1 Nov 2016 08:42:59 -0400 Subject: [PATCH 08/39] document authenticating proxy: --- docs/admin/authentication.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/docs/admin/authentication.md b/docs/admin/authentication.md index 6819677107..6e13c28929 100644 --- a/docs/admin/authentication.md +++ b/docs/admin/authentication.md @@ -33,7 +33,7 @@ or be treated as an anonymous user. ## Authentication strategies -Kubernetes uses client certificates, bearer tokens, or HTTP basic auth to +Kubernetes uses client certificates, bearer tokens, an authenticating proxy, or HTTP basic auth to authenticate API requests through authentication plugins. As HTTP request are made to the API server plugins attempts to associate the following attributes with the request: @@ -360,6 +360,20 @@ An unsuccessful request would return: HTTP status codes can be used to supply additional error context. + +### Authenticating Proxy + +The API server can be configured to identify users from request header values, such as `X-Remote-User`. +It is designed for use in combination with an authenticating proxy, which sets the request header value. +In order to prevent header spoofing, the authenticating proxy is required to present a valid client +certificate to the API server for validation against the specified CA before the request headers are +checked. + +* `--requestheader-username-headers` Required, case-insensitive. Header names to check, in order, for the user identity. The first header containing a value is used as the identity. +* `--requestheader-client-ca-file` Required. PEM-encoded certificate bundle. A valid client certificate must be presented and validated against the certificate authorities in the specified file before the request headers are checked for user names. +* `--requestheader-allowed-names` Optional. List of common names (cn). If set, a valid client certificate with a Common Name (cn) in the specified list must be presented before the request headers are checked for user names. If empty, any Common Name is allowed. + + ### Keystone Password Keystone authentication is enabled by passing the `--experimental-keystone-url=` From 07c0d9298491cbb7de9a15f838180fac5b1fb3e5 Mon Sep 17 00:00:00 2001 From: Matt Baldwin Date: Tue, 1 Nov 2016 15:55:23 -0700 Subject: [PATCH 09/39] Added StackPointCloud as a Technology and Services Partner Change-Id: I04c32a60e447f918aba2d9a27741938a4dcfb434 --- _includes/partner-script.js | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/_includes/partner-script.js b/_includes/partner-script.js index 00dc9f1ee1..3f45a47b4b 100644 --- a/_includes/partner-script.js +++ b/_includes/partner-script.js @@ -14,6 +14,13 @@ link: 'https://deis.com', blurb: 'Deis the creators of Helm, Workflow, and Steward, helps developers and operators build, deploy, manage and scale their applications on top of Kubernetes.' }, + { + type: 0, + name: 'StackPointCloud', + logo: 'stackpointio', + link: 'https://stackpoint.io', + blurb: 'StackPointCloud builds Stackpoint.io, the universal control plane for Kubernetes Anywhere -- compose and build your own infrastructure as easily as a DigitalOcean droplet at any public cloud provider.' + }, { type: 0, name: 'Sysdig Cloud', @@ -168,6 +175,13 @@ link: 'https://deis.com/services/', blurb: 'Deis provides professional services and 24x7 operational support for any Kubernetes cluster managed by our global cluster operations team.' }, + { + type: 1, + name: 'StackPointCloud', + logo: 'stackpoint', + link: 'https://stackpoint.io', + blurb: 'StackPointCloud offers a wide range of support plans for managed Kubernetes clusters built through its universal control plane for Kubernetes Anywhere.' + }, { type: 1, name: 'Samsung SDS', From 0a8408081c8a2805355227994efd16427d1761d4 Mon Sep 17 00:00:00 2001 From: Magnus Kulke Date: Thu, 3 Nov 2016 20:28:51 +0100 Subject: [PATCH 10/39] Updated the NodeHostname entry. --- docs/admin/node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/node.md b/docs/admin/node.md index e7dbbba987..08b5d92f6e 100644 --- a/docs/admin/node.md +++ b/docs/admin/node.md @@ -27,7 +27,7 @@ pieces of information: The usage of these fields varies depending on your cloud provider or bare metal configuration. -* HostName: Generally not used +* HostName: The hostname as reported by the node's kernel. Can be overriden via the kubelet `--hostname-override` parameter. * ExternalIP: Generally the IP address of the node that is externally routable (available from outside the cluster) From 47b59475cc70d25edb8b2f68d021f18e074f32f5 Mon Sep 17 00:00:00 2001 From: Fan Lin Date: Fri, 4 Nov 2016 09:03:48 +0800 Subject: [PATCH 11/39] Add limitation note of using host-port --- docs/admin/network-plugins.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/admin/network-plugins.md b/docs/admin/network-plugins.md index 8cfeb658c9..976e85bd1e 100644 --- a/docs/admin/network-plugins.md +++ b/docs/admin/network-plugins.md @@ -42,6 +42,8 @@ If there are multiple CNI configuration files in the directory, the first one in In addition to the CNI plugin specified by the configuration file, Kubernetes requires the standard CNI `lo` plugin, at minimum version 0.2.0 +Limitation: Due to [#31307](https://github.com/kubernetes/kubernetes/issues/31307), `HostPort` won't work with CNI networking plugin at the moment. That means all `hostPort` attribute in pod would be simply ignored. + ### kubenet The Linux-only kubenet plugin provides functionality similar to the `--configure-cbr0` kubelet command-line option. It creates a Linux bridge named `cbr0` and creates a veth pair for each pod with the host end of each pair connected to `cbr0`. The pod end of the pair is assigned an IP address allocated from a range assigned to the node either through configuration or by the controller-manager. `cbr0` is assigned an MTU matching the smallest MTU of an enabled normal interface on the host. The kubenet plugin is currently mutually exclusive with, and will eventually replace, the --configure-cbr0 option. It is also currently incompatible with the flannel experimental overlay. @@ -72,4 +74,4 @@ This option is provided to the network-plugin; currently **only kubenet supports * `--network-plugin=exec` specifies that we use the `exec` plugin, with executables located in `--network-plugin-dir`. * `--network-plugin=cni` specifies that we use the `cni` network plugin with actual CNI plugin binaries located in `--cni-bin-dir` (default `/opt/cni/bin`) and CNI plugin configuration located in `--cni-conf-dir` (default `/etc/cni/net.d`). * `--network-plugin=kubenet` specifies that we use the `kubenet` network plugin with CNI `bridge` and `host-local` plugins placed in `/opt/cni/bin` or `network-plugin-dir`. -* `--network-plugin-mtu=9001` specifies the MTU to use, currently only used by the `kubenet` network plugin. \ No newline at end of file +* `--network-plugin-mtu=9001` specifies the MTU to use, currently only used by the `kubenet` network plugin. From 38385006efd9954885e2c853ae6d04ed0cfddafa Mon Sep 17 00:00:00 2001 From: Magnus Kulke Date: Fri, 4 Nov 2016 13:56:13 +0100 Subject: [PATCH 12/39] Fixed spelling --- docs/admin/node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/node.md b/docs/admin/node.md index 08b5d92f6e..78ef3c4b2e 100644 --- a/docs/admin/node.md +++ b/docs/admin/node.md @@ -27,7 +27,7 @@ pieces of information: The usage of these fields varies depending on your cloud provider or bare metal configuration. -* HostName: The hostname as reported by the node's kernel. Can be overriden via the kubelet `--hostname-override` parameter. +* HostName: The hostname as reported by the node's kernel. Can be overridden via the kubelet `--hostname-override` parameter. * ExternalIP: Generally the IP address of the node that is externally routable (available from outside the cluster) From a516182f80e9d9df9df9d4a17b428f683b258791 Mon Sep 17 00:00:00 2001 From: Daniel Sachse Date: Fri, 4 Nov 2016 14:44:58 +0100 Subject: [PATCH 13/39] Updated documentation to use beta version of init-containers --- docs/user-guide/nginx-init-containers.yaml | 2 +- docs/user-guide/petset/bootstrapping/petset_peers.yaml | 2 +- docs/user-guide/petset/bootstrapping/petset_vm.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/user-guide/nginx-init-containers.yaml b/docs/user-guide/nginx-init-containers.yaml index 34c20fa66a..24124c7459 100644 --- a/docs/user-guide/nginx-init-containers.yaml +++ b/docs/user-guide/nginx-init-containers.yaml @@ -3,7 +3,7 @@ kind: Pod metadata: name: nginx annotations: - pod.alpha.kubernetes.io/init-containers: '[ + pod.beta.kubernetes.io/init-containers: '[ { "name": "install", "image": "busybox", diff --git a/docs/user-guide/petset/bootstrapping/petset_peers.yaml b/docs/user-guide/petset/bootstrapping/petset_peers.yaml index f8393b5c2c..4f992ead71 100644 --- a/docs/user-guide/petset/bootstrapping/petset_peers.yaml +++ b/docs/user-guide/petset/bootstrapping/petset_peers.yaml @@ -29,7 +29,7 @@ spec: app: nginx annotations: pod.alpha.kubernetes.io/initialized: "true" - pod.alpha.kubernetes.io/init-containers: '[ + pod.beta.kubernetes.io/init-containers: '[ { "name": "peerfinder", "image": "gcr.io/google_containers/peer-finder:0.1", diff --git a/docs/user-guide/petset/bootstrapping/petset_vm.yaml b/docs/user-guide/petset/bootstrapping/petset_vm.yaml index c506a1bac6..a3da5211a3 100644 --- a/docs/user-guide/petset/bootstrapping/petset_vm.yaml +++ b/docs/user-guide/petset/bootstrapping/petset_vm.yaml @@ -27,7 +27,7 @@ spec: app: ub annotations: pod.alpha.kubernetes.io/initialized: "true" - pod.alpha.kubernetes.io/init-containers: '[ + pod.beta.kubernetes.io/init-containers: '[ { "name": "rootfs", "image": "ubuntu:15.10", From bbceda0ba2459fe6f5e02e54642b9d0e94781327 Mon Sep 17 00:00:00 2001 From: blankenhaus Date: Sat, 5 Nov 2016 12:29:50 -0700 Subject: [PATCH 14/39] Layer 3 <=> layer 4 TCP/UDP are layer 4. --- docs/user-guide/services/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/services/index.md b/docs/user-guide/services/index.md index 94faabcd1c..fc7e339dbc 100644 --- a/docs/user-guide/services/index.md +++ b/docs/user-guide/services/index.md @@ -182,7 +182,7 @@ In Kubernetes v1.0 the proxy was purely in userspace. In Kubernetes v1.1 an iptables proxy was added, but was not the default operating mode. Since Kubernetes v1.2, the iptables proxy is the default. -As of Kubernetes v1.0, `Services` are a "layer 3" (TCP/UDP over IP) construct. +As of Kubernetes v1.0, `Services` are a "layer 4" (TCP/UDP over IP) construct. In Kubernetes v1.1 the `Ingress` API was added (beta) to represent "layer 7" (HTTP) services. From 3d7e0b128c67d30ea1f72f043a4ff69bcd4c6fd5 Mon Sep 17 00:00:00 2001 From: Tremaine Eto Date: Mon, 7 Nov 2016 10:16:15 -0800 Subject: [PATCH 15/39] Fixed typo Removed extra "e" in "specify" in the "Secret files permission" section. --- docs/user-guide/secrets/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/secrets/index.md b/docs/user-guide/secrets/index.md index f97c6185b8..c55868f1f1 100644 --- a/docs/user-guide/secrets/index.md +++ b/docs/user-guide/secrets/index.md @@ -265,7 +265,7 @@ All listed keys must exist in the corresponding secret. Otherwise, the volume is **Secret files permissions** You can also specify the permission mode bits files part of a secret will have. -If you don't specify any, `0644` is used by default. You can sepecify a default +If you don't specify any, `0644` is used by default. You can specify a default mode for the whole secret volume and override per key if needed. For example, you can specify a default mode like this: From 215dca8e8ba6764369e7cd30b3cbd650576cb230 Mon Sep 17 00:00:00 2001 From: TRAVIS ALLEN SALAS COX Date: Mon, 7 Nov 2016 13:27:27 -0600 Subject: [PATCH 16/39] Update dns.md This should at least fix a broken link referenced in [#1640](https://github.com/kubernetes/kubernetes.github.io/issues/1640). Looks like a lot of information was taking out of [this](https://github.com/kubernetes/kubernetes/tree/master/build-tools/kube-dns) README.md recently, if you'd like i can delete the reference section completely if it is out of date and/or no longer needed. --- docs/admin/dns.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/dns.md b/docs/admin/dns.md index cc132201aa..82b3bab6c0 100644 --- a/docs/admin/dns.md +++ b/docs/admin/dns.md @@ -216,5 +216,5 @@ supports forward lookups (A records), service lookups (SRV records) and reverse ## References -- [Docs for the DNS cluster addon](http://releases.k8s.io/{{page.githubbranch}}/build/kube-dns/README.md) +- [Docs for the DNS cluster addon](http://releases.k8s.io/{{page.githubbranch}}/build-tools/kube-dns/README.md) From 3ca34c8e0478f503ec5135c53ab23c6206a75a59 Mon Sep 17 00:00:00 2001 From: Steffen Gebert Date: Tue, 8 Nov 2016 11:23:46 +0100 Subject: [PATCH 17/39] configuring-containers: Fix syntax highlight looks weird to me without that.. --- docs/user-guide/configuring-containers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/configuring-containers.md b/docs/user-guide/configuring-containers.md index 6b7b447289..99dc823375 100644 --- a/docs/user-guide/configuring-containers.md +++ b/docs/user-guide/configuring-containers.md @@ -12,7 +12,7 @@ assignees: In addition to the imperative-style commands, such as `kubectl run` and `kubectl expose`, described [elsewhere](/docs/user-guide/quick-start), Kubernetes supports declarative configuration. Oftentimes, configuration files are preferable to imperative commands, since they can be checked into version control and changes to the files can be code reviewed, which is especially important for more complex configurations, producing a more robust, reliable and archival system. -In the declarative style, all configuration is stored in YAML or JSON configuration files using Kubernetes's API resource schemas as the configuration schemas. `kubectl` can create, update, delete, and get API resources. The `apiVersion` (currently 'v1'?), resource `kind`, and resource `name` are used by `kubectl` to construct the appropriate API path to invoke for the specified operation. +In the declarative style, all configuration is stored in YAML or JSON configuration files using Kubernetes's API resource schemas as the configuration schemas. `kubectl` can create, update, delete, and get API resources. The `apiVersion` (currently `v1`?), resource `kind`, and resource `name` are used by `kubectl` to construct the appropriate API path to invoke for the specified operation. ## Launching a container using a configuration file From a3f1880405bc64d1b717b4189b5ce26fdafb2a59 Mon Sep 17 00:00:00 2001 From: Jared Date: Tue, 8 Nov 2016 14:49:02 -0800 Subject: [PATCH 18/39] creating contributing.md Adding a contributing.md file with contributing guidelines for docs on kubernetes.io (https://github.com/blog/1184-contributing-guidelines). This should not be merged until the PR for the docs style guide is merged. (https://github.com/kubernetes/kubernetes.github.io/pull/1619) --- CONTRIBUTING.md | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000000..9dd8149a15 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,36 @@ +# Contributing to Kubernetes Documentation + +**First off, thanks for taking the time to contribute!** + +The following is a set of guidelines for contributing to Kubernetes documentation, hosted at [Kubernetes.io](http://kubernetes.io/). +These are just guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request. + +## Before you get started + +### Code of Conduct + +Kubernetes follows the [Cloud Native Computing Foundation (CNCF) Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to Sarah Novotny [sarahnovotny@google.com](mailto:sarahnovotny@google.com) and/or Dan Kohn [dan@linuxfoundation.org](mailto:dan@linuxfoundation.org). + +### Documentation and Site Decisions + +The [Kubernetes SIG Docs Discussion Group](https://groups.google.com/forum/#!forum/kubernetes-sig-docs) is the discussion group for doc releases, suggested site improvements, and improving the doc contribution experience. If you are planning to be a regular contributor, join this group to stay informed and involved. + +### Style Guides and Templates + +Before submitting a pull request to create new content, please review the [Kubernetes.io style guide](http://kubernetes.io/docs/contribute/style-guide/) and follow the [instructions for using page templates](http://kubernetes.io/docs/contribute/page-templates/). + + +## Contributing to Documentation + +### Reporting Documentation Issues + +Kubernetes.io uses github issues to track documentation issues and requests. If you see a documentation issue, submit an issue using the following steps: + +1. Check the [kubernetes.io issues list](https://github.com/kubernetes/kubernetes.github.io/issues) as you might find out the issue is a duplicate. +2. Use the [included template for every new issue](https://github.com/kubernetes/kubernetes.github.io/issues/new). When you create a bug report, include as many details as possible and include suggested fixes to the issue. + +Note that code issues should be filed against the main kubernetes repository, while documentation issues should go in the kubernetes.io repository. + +### Submitting Documentation Pull Requests + +If you’re fixing an issue in the existing documentation, you should submit a PR against the master branch. Follow [these instructions to create a documentation pull request against the kubernetes.io repository](http://kubernetes.io/docs/contribute/create-pull-request/). From 337c6c054694ce3a75b3607a7a6a220dd3b0c230 Mon Sep 17 00:00:00 2001 From: Brandon DuRette Date: Fri, 11 Nov 2016 11:20:48 -0600 Subject: [PATCH 19/39] Typo fix --- docs/user-guide/thirdpartyresources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/thirdpartyresources.md b/docs/user-guide/thirdpartyresources.md index d8f2bc5ba9..a1035d44c4 100644 --- a/docs/user-guide/thirdpartyresources.md +++ b/docs/user-guide/thirdpartyresources.md @@ -22,7 +22,7 @@ Each `ThirdPartyResource` has the following: * `description` - A free text description of the resource. * `versions` - A list of the versions of the resource. -The `kind` for a `ThirdPartyResource` takes the form `.`. You are expected to provide a unique kind and domain name in order to avoid conflicts with other `ThirdPartyResource` objects. Kind names will be converted to CamelCase when creating instances of the `ThirdPartyResource`. Hypens in the `kind` are assumed to be word breaks. For instance the kind `camel-case` would be converted to `CamelCase` but `camelcase` would be converted to `Camelcase`. +The `kind` for a `ThirdPartyResource` takes the form `.`. You are expected to provide a unique kind and domain name in order to avoid conflicts with other `ThirdPartyResource` objects. Kind names will be converted to CamelCase when creating instances of the `ThirdPartyResource`. Hyphens in the `kind` are assumed to be word breaks. For instance the kind `camel-case` would be converted to `CamelCase` but `camelcase` would be converted to `Camelcase`. Other fields on the `ThirdPartyResource` are treated as custom data fields. These fields can hold arbitrary JSON data and have any structure. From fbba8e49019ad61a809b5a3df781201cf13f631c Mon Sep 17 00:00:00 2001 From: Charlie Drage Date: Mon, 14 Nov 2016 10:54:34 -0500 Subject: [PATCH 20/39] Remove "stars" ratings from each page. This removes the stars rating that appears on the bottom of each page. Doing so also required the update the "a.issue" css that correctly aligns the "Create Issue" button and "Edit this Page" button on the bottom of the page. --- _layouts/docwithnav.html | 2 +- _sass/_base.sass | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/_layouts/docwithnav.html b/_layouts/docwithnav.html index 877ccc4e63..2153d358e2 100755 --- a/_layouts/docwithnav.html +++ b/_layouts/docwithnav.html @@ -41,7 +41,7 @@ {% if notitle != "true" %}

{{ title }}

{% endif %} {{ content }}

Analytics - {% if page.url != "/404.html" and page.url != "/docs/search/" %}

+ {% if page.url != "/404.html" and page.url != "/docs/search/" %}