Add support for operator labels and annotations #2370
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pfmackin
reviewed
May 19, 2021
jshum2479
approved these changes
May 19, 2021
ddsharpe
approved these changes
May 19, 2021
rosemarymarano
approved these changes
May 19, 2021
Contributor
rosemarymarano
left a comment
rosemarymarano
left a comment
There was a problem hiding this comment.
LGTM, minor edits.
| stage: production | ||
| ``` | ||
|
|
||
| You may also specify annotations [using the "--set" parameter to the Helm install command](https://helm.sh/docs/intro/using_helm/#customizing-the-chart-before-installing), as follows: |
Contributor
There was a problem hiding this comment.
"--set" -> Is it possible for this parameter to be in code font, --set? (I forget if it does or does not render correctly when inside a x-ref.) If it works, please make the same edit in the labels section.
| ##### `nodeAffinity` | ||
| Allows you to constrain the operator Pod to be scheduled on a Node with certain labels; it is conceptually similar to `nodeSelector`. `nodeAffinity` provides advanced capabilities to limit Pod placement on specific Nodes. See [Assign Pods to Nodes](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity) in the Kubernetes documentation for more details. This is optional and not required if the operator Pod can run on any Node or when using `nodeSelector`. | ||
| ##### `affinity` | ||
| Allows you to constrain the operator Pod to be scheduled on a Node with certain labels; it is conceptually similar to `nodeSelector`. `affinity` provides advanced capabilities to limit Pod placement on specific Nodes. See [Assign Pods to Nodes](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity) in the Kubernetes documentation for more details. This is optional and not required if the operator Pod can run on any Node or when using `nodeSelector`. |
Contributor
There was a problem hiding this comment.
For more details, see Assign Pods to Nodes in the Kubernetes documentation. (Our Oracle standard format for x-refs to more information.)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A customer was asking for Helm chart values to add labels and annotations to the operator's pod template spec.