From 7c54a74ca1406e100acd16ce0afed1e690d7599d Mon Sep 17 00:00:00 2001 From: Kai Chen Date: Thu, 4 Jan 2018 18:05:27 -0800 Subject: [PATCH] Fix references to ConfigMap for documents in the Tasks section --- .../access-application-cluster/connecting-frontend-backend.md | 4 ++-- docs/tasks/administer-cluster/ip-masq-agent.md | 2 +- docs/tasks/administer-federation/configmap.md | 4 ++-- docs/tasks/configure-pod-container/configure-pod-configmap.md | 2 +- docs/tasks/debug-application-cluster/monitor-node-health.md | 2 +- .../define-command-argument-container.md | 2 +- .../run-application/run-replicated-stateful-application.md | 2 +- 7 files changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/tasks/access-application-cluster/connecting-frontend-backend.md b/docs/tasks/access-application-cluster/connecting-frontend-backend.md index 7b2798a0e1..e2be7e583c 100644 --- a/docs/tasks/access-application-cluster/connecting-frontend-backend.md +++ b/docs/tasks/access-application-cluster/connecting-frontend-backend.md @@ -149,7 +149,7 @@ service "frontend" created **Note**: The nginx configuration is baked into the [container image](/docs/tasks/access-application-cluster/frontend/Dockerfile). A better way to do this would be to use a -[ConfigMap](/docs/tasks/configure-pod-container/configmap/), so +[ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/), so that you can change the configuration more easily. ### Interact with the frontend Service @@ -197,7 +197,7 @@ The output shows the message generated by the backend: {% capture whatsnext %} * Learn more about [Services](/docs/concepts/services-networking/service/) -* Learn more about [ConfigMaps](/docs/tasks/configure-pod-container/configmap/) +* Learn more about [ConfigMaps](/docs/tasks/configure-pod-container/configure-pod-configmap/) {% endcapture %} diff --git a/docs/tasks/administer-cluster/ip-masq-agent.md b/docs/tasks/administer-cluster/ip-masq-agent.md index c18d967dee..f09c868e01 100644 --- a/docs/tasks/administer-cluster/ip-masq-agent.md +++ b/docs/tasks/administer-cluster/ip-masq-agent.md @@ -71,7 +71,7 @@ kubectl label nodes my-node beta.kubernetes.io/masq-agent-ds-ready=true More information can be found in the ip-masq-agent documentation [here](https://github.com/kubernetes-incubator/ip-masq-agent) -In most cases, the default set of rules should be sufficient; however, if this is not the case for your cluster, you can create and apply a [ConfigMap](/docs/tasks/configure-pod-container/configmap/) to customize the IP ranges that are affected. For example, to allow only 10.0.0.0/8 to be considered by the ip-masq-agent, you can create the following [ConfigMap](/docs/tasks/configure-pod-container/configmap/) in a file called "config". +In most cases, the default set of rules should be sufficient; however, if this is not the case for your cluster, you can create and apply a [ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/) to customize the IP ranges that are affected. For example, to allow only 10.0.0.0/8 to be considered by the ip-masq-agent, you can create the following [ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/) in a file called "config". **Note:** It is important that the file is called config since, by default, that will be used as the key for lookup by the ip-masq-agent: ``` diff --git a/docs/tasks/administer-federation/configmap.md b/docs/tasks/administer-federation/configmap.md index 857ea8a59a..0652f73444 100644 --- a/docs/tasks/administer-federation/configmap.md +++ b/docs/tasks/administer-federation/configmap.md @@ -7,7 +7,7 @@ title: Federated ConfigMap This guide explains how to use ConfigMaps in a Federation control plane. Federated ConfigMaps are very similar to the traditional [Kubernetes -ConfigMaps](/docs/tasks/configure-pod-container/configmap/) and provide the same functionality. +ConfigMaps](/docs/tasks/configure-pod-container/configure-pod-configmap/) and provide the same functionality. Creating them in the federation control plane ensures that they are synchronized across all the clusters in federation. @@ -18,7 +18,7 @@ across all the clusters in federation. * {% include federated-task-tutorial-prereqs.md %} * You should also have a basic [working knowledge of Kubernetes](/docs/setup/pick-right-solution/) in -general and [ConfigMaps](/docs/tasks/configure-pod-container/configmap/) in particular. +general and [ConfigMaps](/docs/tasks/configure-pod-container/configure-pod-configmap/) in particular. {% endcapture %} diff --git a/docs/tasks/configure-pod-container/configure-pod-configmap.md b/docs/tasks/configure-pod-container/configure-pod-configmap.md index 1159829a9a..2f8e2d9a97 100644 --- a/docs/tasks/configure-pod-container/configure-pod-configmap.md +++ b/docs/tasks/configure-pod-container/configure-pod-configmap.md @@ -383,7 +383,7 @@ very charm ## Add ConfigMap data to a Volume -As explained in [Configure Containers Using a ConfigMap](/docs/tasks/configure-pod-container/configmap/), when you create a ConfigMap using ``--from-file``, the filename becomes a key stored in the `data` section of the ConfigMap. The file contents become the key's value. +As explained in [Create ConfigMaps from files](#create-configmaps-from-files), when you create a ConfigMap using ``--from-file``, the filename becomes a key stored in the `data` section of the ConfigMap. The file contents become the key's value. The examples in this section refer to a ConfigMap named special-config, shown below. diff --git a/docs/tasks/debug-application-cluster/monitor-node-health.md b/docs/tasks/debug-application-cluster/monitor-node-health.md index 0578d82c1f..7f41339097 100644 --- a/docs/tasks/debug-application-cluster/monitor-node-health.md +++ b/docs/tasks/debug-application-cluster/monitor-node-health.md @@ -120,7 +120,7 @@ Just create `node-problem-detector.yaml`, and put it under the addon pods direct The [default configuration](https://github.com/kubernetes/node-problem-detector/tree/v0.1/config) is embedded when building the docker image of node problem detector. -However, you can use [ConfigMap](/docs/tasks/configure-pod-container/configmap/) to overwrite it +However, you can use [ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/) to overwrite it following the steps: * **Step 1:** Change the config files in `config/`. diff --git a/docs/tasks/inject-data-application/define-command-argument-container.md b/docs/tasks/inject-data-application/define-command-argument-container.md index 65cc657cb0..226b013def 100644 --- a/docs/tasks/inject-data-application/define-command-argument-container.md +++ b/docs/tasks/inject-data-application/define-command-argument-container.md @@ -73,7 +73,7 @@ you can define arguments by using environment variables: This means you can define an argument for a Pod using any of the techniques available for defining environment variables, including -[ConfigMaps](/docs/tasks/configure-pod-container/configmap/) +[ConfigMaps](/docs/tasks/configure-pod-container/configure-pod-configmap/) and [Secrets](/docs/concepts/configuration/secret/). diff --git a/docs/tasks/run-application/run-replicated-stateful-application.md b/docs/tasks/run-application/run-replicated-stateful-application.md index baf7f5e312..1fc7a75364 100644 --- a/docs/tasks/run-application/run-replicated-stateful-application.md +++ b/docs/tasks/run-application/run-replicated-stateful-application.md @@ -31,7 +31,7 @@ on general patterns for running stateful applications in Kubernetes. and [StatefulSets](/docs/concepts/workloads/controllers/statefulset/), as well as other core concepts like [Pods](/docs/concepts/workloads/pods/pod/), [Services](/docs/concepts/services-networking/service/), and - [ConfigMaps](/docs/tasks/configure-pod-container/configmap/). + [ConfigMaps](/docs/tasks/configure-pod-container/configure-pod-configmap/). * Some familiarity with MySQL helps, but this tutorial aims to present general patterns that should be useful for other systems.