Link to appropriate docs for Automatic Mounting of Manually Created Secrets (#3571)

* Update link to Adding ImagePullSecrets to a service account

* Link to appropriate docs for Automatic Mounting of Manually Created Secrets

* Replace here w/ title of pages
This commit is contained in:
Everett Toews
2017-05-01 12:22:51 -05:00
committed by Andrew Chen
parent cfaa556025
commit 937177b991
+4 -5
View File
@@ -136,7 +136,7 @@ encoded as base64 strings. Newlines are not valid within these strings and must
be omitted. When using the `base64` utility on Darwin/OS X users should avoid be omitted. When using the `base64` utility on Darwin/OS X users should avoid
using the `-b` option to split long lines. Conversely Linux users *should* add using the `-b` option to split long lines. Conversely Linux users *should* add
the option `-w 0` to `base64` commands or the pipeline `base64 | tr -d '\n'` if the option `-w 0` to `base64` commands or the pipeline `base64 | tr -d '\n'` if
`-w` option is not available. `-w` option is not available.
#### Decoding a Secret #### Decoding a Secret
@@ -440,15 +440,14 @@ You can manually create an imagePullSecret, and reference it from
a serviceAccount. Any pods created with that serviceAccount a serviceAccount. Any pods created with that serviceAccount
or that default to use that serviceAccount, will get their imagePullSecret or that default to use that serviceAccount, will get their imagePullSecret
field set to that of the service account. field set to that of the service account.
See [here](/docs/user-guide/service-accounts/#adding-imagepullsecrets-to-a-service-account) See [Adding ImagePullSecrets to a service account](/docs/tasks/configure-pod-container/configure-service-account/#adding-imagepullsecrets-to-a-service-account)
for a detailed explanation of that process. for a detailed explanation of that process.
#### Automatic Mounting of Manually Created Secrets #### Automatic Mounting of Manually Created Secrets
We plan to extend the service account behavior so that manually created Manually created secrets (e.g. one containing a token for accessing a github account)
secrets (e.g. one containing a token for accessing a github account)
can be automatically attached to pods based on their service account. can be automatically attached to pods based on their service account.
*This is not implemented yet. See [issue 9902](http://issue.k8s.io/9902).* See [Injecting Information into Pods Using a PodPreset](/docs/tasks/run-application/podpreset/) for a detailed explanation of that process.
## Details ## Details