-
Notifications
You must be signed in to change notification settings - Fork 68
K8SPG-487: add global annotations and labels for cr.yaml
#956
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
Conversation
| if cr.CompareVersion("2.6.0") >= 0 && cr.Spec.Metadata != nil { | ||
| newCASecret.Annotations = cr.Spec.Metadata.Annotations | ||
| newCASecret.Labels = cr.Spec.Metadata.Labels | ||
| } |
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 didn't catch this place, if we will have different annotations (for example for extentions too), should we put it to secret annotations?
deploy/cr.yaml
Outdated
| crVersion: 2.6.0 | ||
| # metadata: | ||
| # annotations: | ||
| # test-annotation: value |
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.
Do we want to have a test prefix here in the CR? Maybe something like example-annotation or annotation-key. Test feels like a leftover from some testing. In all of our examples we never use something like test.
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.
@pooknull wdyt about this?
|
@pooknull pls check unit tests. |
commit: cad7c98 |
https://perconadev.atlassian.net/browse/K8SPG-487
DESCRIPTION
Problem:
It’s not possible to set
annotations/labelsat a global level for all resources created by operator.Solution:
Add
.spec.metadata.labelsand.spec.metadata.annotationsfields to thecr.yaml.CHECKLIST
Jira
Needs Doc) and QA (Needs QA)?Tests
Config/Logging/Testability