-
Notifications
You must be signed in to change notification settings - Fork 14k
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
Edit and redo ConfigMap docs #35160
Edit and redo ConfigMap docs #35160
Conversation
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
/retitle Edit and redo ConfigMap docs We avoid putting PR references (eg #2334) in PR titles. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Some suggestions about the optional ConfigMaps. We shouldn't imply that the behavior is always the same - those optional ConfigMaps might actually exist.
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Outdated
Show resolved
Hide resolved
…nfigmap.md Co-authored-by: Tim Bannister <tim@scalefactory.com>
…nfigmap.md Co-authored-by: Tim Bannister <tim@scalefactory.com>
…nfigmap.md Co-authored-by: Tim Bannister <tim@scalefactory.com>
…nfigmap.md Co-authored-by: Tim Bannister <tim@scalefactory.com>
…nfigmap.md Co-authored-by: Tim Bannister <tim@scalefactory.com>
…nfigmap.md Co-authored-by: Tim Bannister <tim@scalefactory.com>
…nfigmap.md Co-authored-by: Tim Bannister <tim@scalefactory.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shannonxtreme would you like to comment on this one? I know you've been looking at the tech writing in the secrets-and-configmaps area recently.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made some suggestions for clarity. Thank you for this PR :)
@@ -675,7 +657,7 @@ data: | |||
|
|||
### Restrictions | |||
|
|||
- You must create a ConfigMap before referencing it in a Pod specification (unless you mark the ConfigMap as "optional"). If you reference a ConfigMap that doesn't exist, the Pod won't start. Likewise, references to keys that don't exist in the ConfigMap will prevent the pod from starting. | |||
- You must create a ConfigMap before referencing it in a Pod specification, or mark the ConfigMap as "optional" (see [Optional ConfigMaps](#optional-configmaps)). If you reference a ConfigMap that doesn't exist, or hasn't been marked as "optional" the Pod won't start. Likewise, references to keys that don't exist in the ConfigMap will prevent the pod from starting. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feels like this makes the sentence harder to understand.
- You must create a ConfigMap before referencing it in a Pod specification, or mark the ConfigMap as "optional" (see [Optional ConfigMaps](#optional-configmaps)). If you reference a ConfigMap that doesn't exist, or hasn't been marked as "optional" the Pod won't start. Likewise, references to keys that don't exist in the ConfigMap will prevent the pod from starting. | |
- You must create the `ConfigMap` object before you reference it in a Pod specification. Alternatively, mark the ConfigMap reference as `optional` in the Pod spec (see [Optional ConfigMaps](#optional-configmaps)). If you reference a ConfigMap that doesn't exist and you don't mark the reference as `optional`, the Pod won't start. Similarly, references to keys that don't exist in the ConfigMap will also prevent the Pod from starting, unless you mark the key references as `optional`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in ad33b0c
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/configure-pod-container/configure-pod-configmap.md
Outdated
Show resolved
Hide resolved
…nfigmap.md Co-authored-by: Shannon Kularathna <ax3shannonkularathna@gmail.com>
…nfigmap.md Co-authored-by: Shannon Kularathna <ax3shannonkularathna@gmail.com>
Thanks, @shannonxtreme - I have made the updates as suggested. |
Thank you for doing this ! /lgtm |
LGTM label has been added. Git tree hash: 021a8f0ca4d854e3803b3907c632943b56eddfe1
|
No worries, thanks for the feedback and support. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
/approve
In a Pod, or pod template, you can mark a reference to a ConfigMap as _optional_. | ||
If the ConfigMap is non-existent, the configuration for which it provides data in the Pod (e.g. environment variable, mounted volume) will be empty. | ||
You can mark a reference to a ConfigMap as _optional_ in a Pod specification. | ||
If the ConfigMap doesn't exist, the configuration for which it provides data in the Pod (e.g. environment variable, mounted volume) will be empty. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A nit: we avoid Latin phrases and their abbreviations.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Move exiting content on optional ConfigMaps into the "Understanding ConfigMaps and Pods" section to make it more generic (was a sub-section within "Add ConfigMap data to a Volume" and re-worded it slightly.
Also added in content from #2334, which was removed in #2568.
Resolves #9829