Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend secrets docs with key to path mapping and automatic updates #628

Merged
merged 1 commit into from
Jul 7, 2016
Merged

Extend secrets docs with key to path mapping and automatic updates #628

merged 1 commit into from
Jul 7, 2016

Conversation

ingvagabund
Copy link
Contributor

Secret volume plugin has been refactored. Currently, AtomicWritter is used to project all keys.
Allowing to automatically refresh projected secrets.

At the same time, operator can specify target file for each secret and thus override the default projection location.

Cherry-picked from #478.

… mounted secrets.

Secret volume plugin has been refactored. Currently, AtomicWritter is used to project all keys.
Allowing to automatically refresh projected secrets.

Convert level-5 heading into bold heading
@ingvagabund
Copy link
Contributor Author

@johndmulhausen

@johndmulhausen
Copy link

@ingvagabund In PR #478 you refer to this as being intended for the release-1.3 branch, but this is opened against master?

@johndmulhausen
Copy link

Note, if this is not documenting 1.3-specific stuff, we can close this PR regardless. The PR in master will do; everything we do in master will end up in release-1.3. LMK!

@@ -234,6 +280,11 @@ $ cat /etc/foo/password
The program in a container is responsible for reading the secret(s) from the
files.

**Mounted Secrets are updated automatically**
Copy link

@johndmulhausen johndmulhausen Jun 25, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use hashes (which note headings in Markdown) instead of surrounding in asterisks

@ingvagabund
Copy link
Contributor Author

Note, if this is not documenting 1.3-specific stuff, we can close this PR regardless. The PR in master will do; everything we do in master will end up in release-1.3. LMK!

It is, the secret extension was merge in 1.3. That was the reason I created this PR. Again, you asked for it.

@johndmulhausen
Copy link

Merging, marking as to-be-iterated in bug #784

@johndmulhausen johndmulhausen merged commit 12c60af into kubernetes:master Jul 7, 2016
dims pushed a commit to dims/website that referenced this pull request Jan 23, 2023
Okabe-Junya pushed a commit to Okabe-Junya/website that referenced this pull request Dec 4, 2023
…s#628)

Signed-off-by: Dipankar Das <dipsonu10@hotmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants