From 7267a33db7c39564de884f083da1b5def6d36b78 Mon Sep 17 00:00:00 2001 From: scjane Date: Tue, 14 Feb 2017 14:15:27 +0800 Subject: [PATCH 01/11] Update static-pods.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Some of the serial numbers of the ordered list in the "Static pod creation" section are incorrect because items in the list are segmented by code blocks. I think this can be solved in at least the following ways: 1.Remove the ordered list style and just use plain text each beginning with "1", "2"，...,or "step 1", "step 2"，... (My modofication adopts this one) 2.Replace the ordered list with an unordered list in which each item beginning with "step 1", "step 2"，... 3.Use HTML tags, such as
    ,
  1. to give the lists involved Are there any other better ways for this problem? I would be appreciated to know. --- docs/admin/static-pods.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/admin/static-pods.md b/docs/admin/static-pods.md index 8c9e482d0d..7ac6e7c890 100644 --- a/docs/admin/static-pods.md +++ b/docs/admin/static-pods.md @@ -20,13 +20,13 @@ The configuration files are just standard pod definition in json or yaml format For example, this is how to start a simple web server as a static pod: -1. Choose a node where we want to run the static pod. In this example, it's `my-node1`. +1.Choose a node where we want to run the static pod. In this example, it's `my-node1`. ```shell [joe@host ~] $ ssh my-node1 ``` -2. Choose a directory, say `/etc/kubelet.d` and place a web server pod definition there, e.g. `/etc/kubernetes.d/static-web.yaml`: +2.Choose a directory, say `/etc/kubelet.d` and place a web server pod definition there, e.g. `/etc/kubernetes.d/static-web.yaml`: ```shell [root@my-node1 ~] $ mkdir /etc/kubernetes.d/ @@ -48,7 +48,7 @@ spec: EOF ``` -2. Configure your kubelet daemon on the node to use this directory by running it with `--pod-manifest-path=/etc/kubelet.d/` argument. On Fedora edit `/etc/kubernetes/kubelet` to include this line: +3.Configure your kubelet daemon on the node to use this directory by running it with `--pod-manifest-path=/etc/kubelet.d/` argument. On Fedora edit `/etc/kubernetes/kubelet` to include this line: ```conf KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --pod-manifest-path=/etc/kubelet.d/" @@ -56,7 +56,7 @@ KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --pod-manife Instructions for other distributions or Kubernetes installations may vary. -3. Restart kubelet. On Fedora, this is: +4.Restart kubelet. On Fedora, this is: ```shell [root@my-node1 ~] $ systemctl restart kubelet From dd595ae05b225330f1e8f91de3ae78f11c631be1 Mon Sep 17 00:00:00 2001 From: Wang Jie Date: Tue, 28 Feb 2017 18:57:54 +0800 Subject: [PATCH 02/11] Update static-pods.md It works. Please review it again. --- docs/admin/static-pods.md | 65 ++++++++++++++++++++------------------- 1 file changed, 33 insertions(+), 32 deletions(-) diff --git a/docs/admin/static-pods.md b/docs/admin/static-pods.md index 7ac6e7c890..44e7134af5 100644 --- a/docs/admin/static-pods.md +++ b/docs/admin/static-pods.md @@ -20,47 +20,48 @@ The configuration files are just standard pod definition in json or yaml format For example, this is how to start a simple web server as a static pod: -1.Choose a node where we want to run the static pod. In this example, it's `my-node1`. +1. Choose a node where we want to run the static pod. In this example, it's `my-node1`. -```shell -[joe@host ~] $ ssh my-node1 -``` + ``` + [joe@host ~] $ ssh my-node1 + ``` -2.Choose a directory, say `/etc/kubelet.d` and place a web server pod definition there, e.g. `/etc/kubernetes.d/static-web.yaml`: +2. Choose a directory, say `/etc/kubelet.d` and place a web server pod definition there, e.g. `/etc/kubernetes.d/static-web.yaml`: -```shell -[root@my-node1 ~] $ mkdir /etc/kubernetes.d/ -[root@my-node1 ~] $ cat </etc/kubernetes.d/static-web.yaml -apiVersion: v1 -kind: Pod -metadata: - name: static-web - labels: - role: myrole -spec: - containers: - - name: web - image: nginx - ports: + ``` + [root@my-node1 ~] $ mkdir /etc/kubernetes.d/ + [root@my-node1 ~] $ cat </etc/kubernetes.d/static-web.yaml + apiVersion: v1 + kind: Pod + metadata: + name: static-web + labels: + role: myrole + spec: + containers: - name: web - containerPort: 80 - protocol: TCP -EOF -``` + image: nginx + ports: + - name: web + containerPort: 80 + protocol: TCP + EOF + ``` -3.Configure your kubelet daemon on the node to use this directory by running it with `--pod-manifest-path=/etc/kubelet.d/` argument. On Fedora edit `/etc/kubernetes/kubelet` to include this line: +3. Configure your kubelet daemon on the node to use this directory by running it with `--pod-manifest-path=/etc/kubelet.d/` argument. + On Fedora edit `/etc/kubernetes/kubelet` to include this line: -```conf -KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --pod-manifest-path=/etc/kubelet.d/" -``` + ```conf + KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --pod-manifest-path=/etc/kubelet.d/" + ``` -Instructions for other distributions or Kubernetes installations may vary. + Instructions for other distributions or Kubernetes installations may vary. -4.Restart kubelet. On Fedora, this is: +4. Restart kubelet. On Fedora, this is: -```shell -[root@my-node1 ~] $ systemctl restart kubelet -``` + ``` + [root@my-node1 ~] $ systemctl restart kubelet + ``` ## Pods created via HTTP From 8ab16cb669aa6f7e1f4d480d05e15eac24af10e6 Mon Sep 17 00:00:00 2001 From: steveperry-53 Date: Tue, 28 Feb 2017 10:52:54 -0800 Subject: [PATCH 03/11] Prototype for deprecating User Guide topic. --- _data/guides.yml | 1 - .../run-stateless-application-deployment.md | 3 +++ docs/user-guide/simple-nginx.md | 7 ------- robots.txt | 1 + 4 files changed, 4 insertions(+), 8 deletions(-) delete mode 100644 docs/user-guide/simple-nginx.md diff --git a/_data/guides.yml b/_data/guides.yml index 30ee93078c..df3ebad90a 100644 --- a/_data/guides.yml +++ b/_data/guides.yml @@ -56,7 +56,6 @@ toc: - title: Containers and Pods section: - - docs/user-guide/simple-nginx.md - docs/user-guide/pods/single-container.md - docs/user-guide/pods/multi-container.md - docs/user-guide/pods/init-container.md diff --git a/docs/tutorials/stateless-application/run-stateless-application-deployment.md b/docs/tutorials/stateless-application/run-stateless-application-deployment.md index 8e3d725752..2b9793bfa4 100644 --- a/docs/tutorials/stateless-application/run-stateless-application-deployment.md +++ b/docs/tutorials/stateless-application/run-stateless-application-deployment.md @@ -1,5 +1,8 @@ --- title: Running a Stateless Application Using a Deployment +redirect_from: +- "/docs/user-guide/simple-nginx/" +- "/docs/user-guide/simple-nginx.html" --- {% capture overview %} diff --git a/docs/user-guide/simple-nginx.md b/docs/user-guide/simple-nginx.md deleted file mode 100644 index 2a6b11133f..0000000000 --- a/docs/user-guide/simple-nginx.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: Running Your First Containers ---- - -{% include user-guide-content-moved.md %} - -[Running a Stateless Application Using a Deployment](/docs/tutorials/stateless-application/run-stateless-application-deployment/) diff --git a/robots.txt b/robots.txt index 9bb39d8dbd..10fff656d2 100644 --- a/robots.txt +++ b/robots.txt @@ -5,5 +5,6 @@ Disallow: /v1.0/ Disallow: /v1.1/ Disallow: /404/ Disallow: 404.html +Disallow: /docs/user-guide/docs/user-guide/simple-nginx/ SITEMAP: http://kubernetes.io/sitemap.xml From 04f2e50caa59ebcfb5db461f65b6733bbf8f2a9e Mon Sep 17 00:00:00 2001 From: Philipp T Date: Tue, 28 Feb 2017 21:53:38 +0100 Subject: [PATCH 04/11] missing word The return of the OCD. --- docs/concepts/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/index.md b/docs/concepts/index.md index 8e738e809e..39e44fbc97 100644 --- a/docs/concepts/index.md +++ b/docs/concepts/index.md @@ -8,7 +8,7 @@ The Concepts section helps you learn about the parts of the Kubernetes system an To work with Kubernetes, you use *Kubernetes API objects* to describe your cluster's *desired state*: what applications or other workloads you want to run, what container images they use, the number of replicas, what network and disk resources you want to make available, and more. You set your desired state by creating objects using the Kubernetes API, typically via the command-line interface, `kubectl`. You can also use the Kubernetes API directly to interact with the cluster and set or modify your desired state. -Once you've set your desired state, the *Kubernetes Control Plane* works to make the cluster's current state match the desired state. To do so, Kuberentes performs a variety of tasks automatically--such as starting or restarting containers, scaling the number of replicas of a given application, and more. The Kubernetes Control Plane consists of a collection processes running on your cluster: +Once you've set your desired state, the *Kubernetes Control Plane* works to make the cluster's current state match the desired state. To do so, Kuberentes performs a variety of tasks automatically--such as starting or restarting containers, scaling the number of replicas of a given application, and more. The Kubernetes Control Plane consists of a collection of processes running on your cluster: * The **Kubernetes Master** is a collection of four processes that run on a single node in your cluster, which is designated as the master node. * Each individual non-master node in your cluster runs two processes: From 1564ae52b76ea4dd090dfe5ac9b6c61bf9cb41ec Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Tue, 28 Feb 2017 19:05:31 -0800 Subject: [PATCH 05/11] Move Guide topic: Using Environment Variables. (#2645) --- docs/user-guide/environment-guide/index.md | 95 +--------------------- 1 file changed, 2 insertions(+), 93 deletions(-) diff --git a/docs/user-guide/environment-guide/index.md b/docs/user-guide/environment-guide/index.md index cbdd806ecd..9db0f41f9b 100644 --- a/docs/user-guide/environment-guide/index.md +++ b/docs/user-guide/environment-guide/index.md @@ -4,97 +4,6 @@ assignees: title: Using Environment Variables --- -This example demonstrates running pods, replication controllers, and -services. It shows two types of pods: frontend and backend, with -services on top of both. Accessing the frontend pod will return -environment information about itself, and a backend pod that it has -accessed through the service. The goal is to illuminate the -environment metadata available to running containers inside the -Kubernetes cluster. The documentation for the Kubernetes environment -is [here](/docs/user-guide/container-environment). +{% include user-guide-content-moved.md %} -![Diagram](/images/docs/diagram.png) - -## Prerequisites - -This example assumes that you have a Kubernetes cluster installed and -running, and that you have installed the `kubectl` command line tool -somewhere in your path. Please see the [getting -started](/docs/getting-started-guides/) for installation instructions -for your platform. - -## Optional: Build your own containers - -These are the configuration files for the containers: - -* [backend-rc.yaml](https://raw.githubusercontent.com/kubernetes/kubernetes.github.io/master/docs/user-guide/environment-guide/backend-rc.yaml) -* [backend-srv.yaml](https://raw.githubusercontent.com/kubernetes/kubernetes.github.io/master/docs/user-guide/environment-guide/backend-srv.yaml) -* [show-rc.yaml](https://raw.githubusercontent.com/kubernetes/kubernetes.github.io/master/docs/user-guide/environment-guide/show-rc.yaml) -* [show-srv.yaml](https://raw.githubusercontent.com/kubernetes/kubernetes.github.io/master/docs/user-guide/environment-guide/show-srv.yaml) - -## Get everything running - -```shell -kubectl create -f ./backend-rc.yaml -kubectl create -f ./backend-srv.yaml -kubectl create -f ./show-rc.yaml -kubectl create -f ./show-srv.yaml -``` - -## Query the service - -Use `kubectl describe service show-srv` to determine the public IP of -your service. - -> Note: If your platform does not support external load balancers, - you'll need to open the proper port and direct traffic to the - internal IP shown for the frontend service with the above command - -Run `curl :80` to query the service. You should get -something like this back: - -```shell -Pod Name: show-rc-xxu6i -Pod Namespace: default -USER_VAR: important information - -Kubernetes environment variables -BACKEND_SRV_SERVICE_HOST = 10.147.252.185 -BACKEND_SRV_SERVICE_PORT = 5000 -KUBERNETES_RO_SERVICE_HOST = 10.147.240.1 -KUBERNETES_RO_SERVICE_PORT = 80 -KUBERNETES_SERVICE_HOST = 10.147.240.2 -KUBERNETES_SERVICE_PORT = 443 -KUBE_DNS_SERVICE_HOST = 10.147.240.10 -KUBE_DNS_SERVICE_PORT = 53 - -Found backend ip: 10.147.252.185 port: 5000 -Response from backend -Backend Container -Backend Pod Name: backend-rc-6qiya -Backend Namespace: default -``` - -First the frontend pod's information is printed. The pod name and -[namespace](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/namespaces.md) are retrieved from the -[Downward API](/docs/user-guide/downward-api). Next, `USER_VAR` is the name of -an environment variable set in the [pod -definition](https://raw.githubusercontent.com/kubernetes/kubernetes.github.io/master/docs/user-guide/environment-guide/show-rc.yaml). Then, the dynamic Kubernetes environment -variables are scanned and printed. These are used to find the backend -service, named `backend-srv`. Finally, the frontend pod queries the -backend service and prints the information returned. Again the backend -pod returns its own pod name and namespace. - -Try running the `curl` command a few times, and notice what -changes. Ex: `watch -n 1 curl -s ` Firstly, the frontend service -is directing your request to different frontend pods each time. The -frontend pods are always contacting the backend through the backend -service. This results in a different backend pod servicing each -request as well. - -## Cleanup - -```shell -kubectl delete rc,service -l type=show-type -kubectl delete rc,service -l type=backend-type -``` +[Exposing Pod Information to Containers Through Environment Variables](/docs/tasks/configure-pod-container/environment-variable-expose-pod-information/) From b9ca35076b5afd4fb2b282167340d4c8c17908e4 Mon Sep 17 00:00:00 2001 From: tanshanshan Date: Thu, 2 Mar 2017 00:26:42 +0800 Subject: [PATCH 06/11] fix typo (#2656) fix typo --- docs/admin/namespaces/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/admin/namespaces/index.md b/docs/admin/namespaces/index.md index 887f14cd91..8da2107960 100644 --- a/docs/admin/namespaces/index.md +++ b/docs/admin/namespaces/index.md @@ -44,9 +44,9 @@ You can list the current namespaces in a cluster using: ```shell $ kubectl get namespaces -NAME LABELS STATUS -default Active -kube-system Active +NAME STATUS AGE +default Active 11d +kube-system Active 11d ``` Kubernetes starts with two initial namespaces: From a2fbc82bd08451951929ea19f792dc86530c4063 Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Wed, 1 Mar 2017 08:55:15 -0800 Subject: [PATCH 07/11] Move Guide topic: Using Port Forwarding. (#2661) --- ...connecting-to-applications-port-forward.md | 44 +------------------ 1 file changed, 2 insertions(+), 42 deletions(-) diff --git a/docs/user-guide/connecting-to-applications-port-forward.md b/docs/user-guide/connecting-to-applications-port-forward.md index 4855994736..afa3559eba 100644 --- a/docs/user-guide/connecting-to-applications-port-forward.md +++ b/docs/user-guide/connecting-to-applications-port-forward.md @@ -5,46 +5,6 @@ assignees: title: Connect with Port Forwarding --- -kubectl port-forward forwards connections to a local port to a port on a pod. Its man page is available [here](/docs/user-guide/kubectl/kubectl_port-forward). Compared to [kubectl proxy](/docs/user-guide/accessing-the-cluster/#using-kubectl-proxy), `kubectl port-forward` is more generic as it can forward TCP traffic while `kubectl proxy` can only forward HTTP traffic. This guide demonstrates how to use `kubectl port-forward` to connect to a Redis database, which may be useful for database debugging. +{% include user-guide-content-moved.md %} -## Creating a Redis master - -```shell -$ kubectl create -f examples/redis/redis-master.yaml -pods/redis-master -``` - -wait until the Redis master pod is Running and Ready, - -```shell -$ kubectl get pods -NAME READY STATUS RESTARTS AGE -redis-master 2/2 Running 0 41s -``` - -## Connecting to the Redis master[a] - -The Redis master is listening on port 6379, to verify this, - -```shell{% raw %} -$ kubectl get pods redis-master --template='{{(index (index .spec.containers 0).ports 0).containerPort}}{{"\n"}}' -6379{% endraw %} -``` - -then we forward the port 6379 on the local workstation to the port 6379 of pod redis-master, - -```shell -$ kubectl port-forward redis-master 6379:6379 -I0710 14:43:38.274550 3655 portforward.go:225] Forwarding from 127.0.0.1:6379 -> 6379 -I0710 14:43:38.274797 3655 portforward.go:225] Forwarding from [::1]:6379 -> 6379 -``` - -To verify the connection is successful, we run a redis-cli on the local workstation, - -```shell -$ redis-cli -127.0.0.1:6379> ping -PONG -``` - -Now one can debug the database from the local workstation. +[Using Port Forwarding to Access Applications in a Cluster](/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) From a642102dc8b8e83175f2918613041ca424a2c09d Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Wed, 1 Mar 2017 09:20:52 -0800 Subject: [PATCH 08/11] Move Guide topic: Bootstrapping Pet Sets. (#2662) * Move Guide topic: Bootstrapping Pet Sets. * Add TOC entry. --- _data/concepts.yml | 1 + docs/concepts/abstractions/controllers/petsets.md | 15 +++++++++++++++ docs/user-guide/petset/bootstrapping/index.md | 6 ++++-- 3 files changed, 20 insertions(+), 2 deletions(-) create mode 100644 docs/concepts/abstractions/controllers/petsets.md diff --git a/_data/concepts.yml b/_data/concepts.yml index bd187c6cee..440f9dbf2b 100644 --- a/_data/concepts.yml +++ b/_data/concepts.yml @@ -20,6 +20,7 @@ toc: - title: Controllers section: - docs/concepts/abstractions/controllers/statefulsets.md + - docs/concepts/abstractions/controllers/petsets.md - docs/concepts/abstractions/controllers/garbage-collection.md - title: Object Metadata diff --git a/docs/concepts/abstractions/controllers/petsets.md b/docs/concepts/abstractions/controllers/petsets.md new file mode 100644 index 0000000000..760e7e882a --- /dev/null +++ b/docs/concepts/abstractions/controllers/petsets.md @@ -0,0 +1,15 @@ +--- +assignees: +- bprashanth +- enisoc +- erictune +- foxish +- janetkuo +- kow3ns +- smarterclayton +title: PetSets +--- + +__Warning:__ Starting in Kubernetes version 1.5, PetSet has been renamed to [StatefulSet](/docs/concepts/abstractions/controllers/statefulsets). To use (or continue to use) PetSet in Kubernetes 1.5, you _must_ [migrate](/docs/tasks/manage-stateful-set/upgrade-pet-set-to-stateful-set/) your existing PetSets to StatefulSets. For information on working with StatefulSet, see the tutorial on [how to run replicated stateful applications](/docs/tutorials/stateful-application/run-replicated-stateful-application). + +__This document has been deprecated__. diff --git a/docs/user-guide/petset/bootstrapping/index.md b/docs/user-guide/petset/bootstrapping/index.md index de3ccb4bd8..1988cba12a 100644 --- a/docs/user-guide/petset/bootstrapping/index.md +++ b/docs/user-guide/petset/bootstrapping/index.md @@ -10,7 +10,9 @@ assignees: title: Bootstrapping Pet Sets --- -__Warning:__ Starting in Kubernetes version 1.5, PetSet has been renamed to [StatefulSet](/docs/concepts/abstractions/controllers/statefulsets). To use (or continue to use) PetSet in Kubernetes 1.5, you _must_ [migrate](/docs/tasks/manage-stateful-set/upgrade-pet-set-to-stateful-set/) your existing PetSets to StatefulSets. For information on working with StatefulSet, see the tutorial on [how to run replicated stateful applications](/docs/tutorials/stateful-application/run-replicated-stateful-application). +{% include user-guide-content-moved.md %} + +[PetSets](/docs/concepts/abstractions/controllers/petsets/) + -__This document has been deprecated__. From 6b675d9b69e1a5f6f36307c08f818f63516805d8 Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Wed, 1 Mar 2017 09:42:05 -0800 Subject: [PATCH 09/11] Move Guide topic: Connect with Proxies. (#2663) * Move Guide topic: Connect with Proxies. * Fix link. --- .../connecting-to-applications-proxy.md | 26 ++----------------- 1 file changed, 2 insertions(+), 24 deletions(-) diff --git a/docs/user-guide/connecting-to-applications-proxy.md b/docs/user-guide/connecting-to-applications-proxy.md index 559b06da9f..a95c2b06a2 100644 --- a/docs/user-guide/connecting-to-applications-proxy.md +++ b/docs/user-guide/connecting-to-applications-proxy.md @@ -5,28 +5,6 @@ assignees: title: Connect with Proxies --- -You have seen the [basics](/docs/user-guide/accessing-the-cluster) about `kubectl proxy` and `apiserver proxy`. This guide shows how to use them together to access a service([kube-ui](/docs/user-guide/ui)) running on the Kubernetes cluster from your workstation. +{% include user-guide-content-moved.md %} - -## Getting the apiserver proxy URL of kube-ui - -kube-ui is deployed as a cluster add-on. To find its apiserver proxy URL, - -```shell -$ kubectl cluster-info | grep "KubeUI" -KubeUI is running at https://173.255.119.104/api/v1/proxy/namespaces/kube-system/services/kube-ui -``` - -if this command does not find the URL, try the steps [here](/docs/user-guide/ui/#accessing-the-ui). - - -## Connecting to the kube-ui service from your local workstation - -The above proxy URL is an access to the kube-ui service provided by the apiserver. To access it, you still need to authenticate to the apiserver. `kubectl proxy` can handle the authentication. - -```shell -$ kubectl proxy --port=8001 -Starting to serve on localhost:8001 -``` - -Now you can access the kube-ui service on your local workstation at [http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kube-ui](http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kube-ui) \ No newline at end of file +[Using an HTTP Proxy to Access the Kubernetes API](/docs/tasks/access-kubernetes-api/http-proxy-access-api/) From 06416ac6e8f4ba2c0ddbf36582b4d03e1de88e33 Mon Sep 17 00:00:00 2001 From: xilabao Date: Tue, 28 Feb 2017 13:55:54 +0800 Subject: [PATCH 10/11] add DefaultTolerationSeconds admission controller --- docs/admin/admission-controllers.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/admin/admission-controllers.md b/docs/admin/admission-controllers.md index 089dce2605..29429c5b2c 100644 --- a/docs/admin/admission-controllers.md +++ b/docs/admin/admission-controllers.md @@ -252,6 +252,11 @@ This plugin ignores any `PersistentVolumeClaim` updates, it acts only on creatio See [persistent volume](/docs/user-guide/persistent-volumes) documentation about persistent volume claims and storage classes and how to mark a storage class as default. +### DefaultTolerationSeconds + +This plug-in sets the default forgiveness toleration for pods, which have no forgiveness tolerations, to tolerate +the taints `notready:NoExecute` and `unreachable:NoExecute` for 5 minutes. + ## Is there a recommended set of plug-ins to use? Yes. From c3e5ad74c51a3e43d14ff4de600f253b5a353a49 Mon Sep 17 00:00:00 2001 From: Rob Szumski Date: Thu, 23 Feb 2017 17:00:25 -0800 Subject: [PATCH 11/11] getting-started-guides: add CoreOS Tectonic --- docs/getting-started-guides/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/getting-started-guides/index.md b/docs/getting-started-guides/index.md index 4ed17d4f47..2d3d18cd57 100644 --- a/docs/getting-started-guides/index.md +++ b/docs/getting-started-guides/index.md @@ -61,6 +61,7 @@ few commands, and have active community support. - [GCE](/docs/getting-started-guides/gce) - [AWS](/docs/getting-started-guides/aws) - [Azure](/docs/getting-started-guides/azure) +- [Tectonic by CoreOS](https://coreos.com/tectonic) - [CenturyLink Cloud](/docs/getting-started-guides/clc) - [IBM SoftLayer](https://github.com/patrocinio/kubernetes-softlayer) - [Stackpoint.io](/docs/getting-started-guides/stackpoint/)