Pvcprotection toc (#7807)

* Refreshing installation instructions (#7495) * Refreshing installation instructions Added conjure-up. Updated displays and juju versions to current versions. * Updated anchors * Fixed image value version typo (#7768) Was inconsistent with other values * Update flocker reference to the github repo (#7784) * Fix typo in federation document (#7779) * an user -> a user (#7778) * Events are namespaced (#7767) * fix 'monitoring' link lose efficacy problem' (#7764) * docs/concepts/policy/pod-security-policy.md: minor fix. (#7659) * Update downward-api-volume-expose-pod-information.md (#7771) * Update downward-api-volume-expose-pod-information.md The pod spec puts the downward api files into /etc/podinfo, not directly in /etc. Updated docs to reflect this fact. * Update downward-api-volume-expose-pod-information.md One more spot needed fixing. * Update downward-api-volume-expose-pod-information.md Yet another fix, in the container example. * Add Amadeus Case Study (#7783) * Add Amadeus Case Study * add Amadeus logo * Fixed Cyrillic с in 'kube-proxy-cm' (#7787) There was a typo (wrong character) in kube-proxy-cm.yaml - Cyrillic с (UTF-8 0x0441) was used instead of Latin c. * install-kubectl: choose one installation method (#7705) The previous text layout suggested that all installations had to be done, one after another. * Update install-kubeadm.md (#7781) Add note to kubeadm install instruction to help install in other arch i.e. aarch64, ppc64le etc. * repair failure link (#7788) * repair failure link * repair failure link * do change as required * Update k8s201.md (#7777) * Update k8s201.md Change instructions to download yams files directly from the website (as used in other pages.) Added instructions to delete labeled pod to avoid warnings in the subsequent deployment step. * Update k8s201.md Added example of using the exposed host from the a node running Kubernetes. (This works on AWS with Weave; not able to test it on other variations...) * Gramatical fix to kompose introduction (#7792) The original wording didn't through very well. As much of the original sentence has been preserved as possible, primarily to ensure the kompose web address is see both in text and as a href link. * update amadeus.html (#7800) * Fix a missing word in endpoint reconciler section (#7804) * add toc entry for pvcprotection downgrade issue doc
2018-03-21 14:30:04 -07:00
parent acdcf705e2
commit 77eaeda923
25 changed files with 708 additions and 89 deletions
@@ -386,7 +386,7 @@ To join clusters into the federation:

 1. If you are using a managed cluster service, allow the service to access the cluster. To do this, create a `clusterrolebinding` for the account associated with your cluster service:

-       kubectl create clusterrolebinding <your_user>-cluster-admin-binding --clusterrole=cluster-admin --user=<your_user>@example.org --context=<joining_cluster_context
+       kubectl create clusterrolebinding <your_user>-cluster-admin-binding --clusterrole=cluster-admin --user=<your_user>@example.org --context=<joining_cluster_context>

 1. Join the cluster to the federation, using `kubefed join`, and make sure you provide the following:

@@ -37,7 +37,7 @@ Here is the configuration file for the Pod:
 {% include code.html language="yaml" file="dapi-volume.yaml" ghlink="/docs/tasks/inject-data-application/dapi-volume.yaml" %}

 In the configuration file, you can see that the Pod has a `downwardAPI` Volume,
-and the Container mounts the Volume at `/etc`.
+and the Container mounts the Volume at `/etc/podinfo`.

 Look at the `items` array under `downwardAPI`. Each element of the array is a
 [DownwardAPIVolumeFile](/docs/api-reference/{{page.version}}/#downwardapivolumefile-v1-core).
@@ -88,7 +88,7 @@ kubectl exec -it kubernetes-downwardapi-volume-example -- sh
 In your shell, view the `labels` file:

 ```shell
-/# cat /etc/labels
+/# cat /etc/podinfo/labels
 ```

 The output shows that all of the Pod's labels have been written
@@ -103,19 +103,19 @@ zone="us-est-coast"
 Similarly, view the `annotations` file:

 ```shell
-/# cat /etc/annotations
+/# cat /etc/podinfo/annotations
 ```

-View the files in the `/etc` directory:
+View the files in the `/etc/podinfo` directory:

 ```shell
-/# ls -laR /etc
+/# ls -laR /etc/podinfo
 ```

 In the output, you can see that the `labels` and `annotations` files
 are in a temporary subdirectory: in this example,
-`..2982_06_02_21_47_53.299460680`. In the `/etc` directory, `..data` is
-a symbolic link to the temporary subdirectory. Also in  the `/etc` directory,
+`..2982_06_02_21_47_53.299460680`. In the `/etc/podinfo` directory, `..data` is
+a symbolic link to the temporary subdirectory. Also in  the `/etc/podinfo` directory,
 `labels` and `annotations` are symbolic links.

 ```
@@ -155,7 +155,7 @@ file for a Pod that has one Container:
 {% include code.html language="yaml" file="dapi-volume-resources.yaml" ghlink="/docs/tasks/inject-data-application/dapi-volume-resources.yaml" %}

 In the configuration file, you can see that the Pod has a `downwardAPI` Volume,
-and the Container mounts the Volume at `/etc`.
+and the Container mounts the Volume at `/etc/podinfo`.

 Look at the `items` array under `downwardAPI`. Each element of the array is a
 DownwardAPIVolumeFile.
@@ -179,7 +179,7 @@ kubectl exec -it kubernetes-downwardapi-volume-example-2 -- sh
 In your shell, view the `cpu_limit` file:

 ```shell
-/# cat /etc/cpu_limit
+/# cat /etc/podinfo/cpu_limit
 ```
 You can use similar commands to view the `cpu_request`, `mem_limit` and
 `mem_request` files.
@@ -13,9 +13,13 @@ Use the Kubernetes command-line tool, [kubectl](/docs/user-guide/kubectl/), to d
 Use a version of kubectl that is the same version as your server or later. Using an older kubectl with a newer server might produce validation errors.
 {% endcapture %}

+## Install kubectl
+
 Here are a few methods to install kubectl.
+Pick the one that suits your environment best.
+
 {% capture steps %}
-## Install kubectl binary via curl
+### Install kubectl binary via curl

 {% capture macos %}
 1. Download the latest release with the command:
@@ -83,7 +87,7 @@ Here are a few methods to install kubectl.

 {% include tabs.md %}

-## Download as part of the Google Cloud SDK
+### Download as part of the Google Cloud SDK

 kubectl can be installed as part of the Google Cloud SDK.

@@ -94,7 +98,7 @@ kubectl can be installed as part of the Google Cloud SDK.

 3. Run `kubectl version` to verify that the version you've installed is sufficiently up-to-date.

-## Install with snap on Ubuntu
+### Install with snap on Ubuntu

 kubectl is available as a [snap](https://snapcraft.io/) application.

@@ -104,7 +108,7 @@ kubectl is available as a [snap](https://snapcraft.io/) application.

 2. Run `kubectl version` to verify that the version you've installed is sufficiently up-to-date.

-## Install with Homebrew on macOS
+### Install with Homebrew on macOS

 1. If you are on macOS and using [Homebrew](https://brew.sh/) package manager, you can install with:

@@ -112,7 +116,7 @@ kubectl is available as a [snap](https://snapcraft.io/) application.

 2. Run `kubectl version` to verify that the version you've installed is sufficiently up-to-date.

-## Install with Powershell from PSGallery
+### Install with Powershell from PSGallery

 1. If you are on Windows and using [Powershell Gallery](https://www.powershellgallery.com/) package manager, you can install and update with:

@@ -125,7 +129,7 @@ If no Downloadlocation is specified, kubectl will be installed in users temp Dir
 re-run Install-Script to update the installer
 re-run install-kubectl.ps1 to install latest binaries

-## Install with Chocolatey on Windows
+### Install with Chocolatey on Windows

 1. If you are on Windows and using [Chocolatey](https://chocolatey.org) package manager, you can install with: