diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2017-11-23 04:24:38 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-11-23 04:24:38 -0800 |
| commit | df17ea18e86fc29409ef6d80813f7b0dac769da5 (patch) | |
| tree | 815847e7dfb9d7775195d3238501cc752ec26abc | |
| parent | 33e0e9a29b6232dff69a98822c66c47331d5fdb2 (diff) | |
| parent | 33ae28c959023fe7a6d72835f738f83ec5378e59 (diff) | |
Merge pull request #1429 from YanTingLittleCute/patch-14
Automatic merge from submit-queue.
Update pod-preset.md
| -rw-r--r-- | contributors/design-proposals/service-catalog/pod-preset.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/service-catalog/pod-preset.md b/contributors/design-proposals/service-catalog/pod-preset.md index 53da4dd9..cf5a654f 100644 --- a/contributors/design-proposals/service-catalog/pod-preset.md +++ b/contributors/design-proposals/service-catalog/pod-preset.md @@ -69,7 +69,7 @@ information into every pod spec where it is needed. 2. Database Administrator creates secrets for the cluster containing the database name, username, and password. 3. Database Administrator creates a `PodPreset` defining the database - port as an enviornment variable, as well as the secrets. See + port as an environment variable, as well as the secrets. See [Examples](#examples) below for various examples. 4. Developer of an application can now label their pod with the specified `Selector` the Database Administrator tells them, and consume the MySQL |