Conversation
| } | ||
| l := naming.Labels() | ||
| l[naming.LabelInstance] = cr.Name | ||
| l[naming.LabelManagedBy] = "percona-server-operator" |
There was a problem hiding this comment.
| l[naming.LabelManagedBy] = "percona-server-operator" | |
| l[naming.LabelManagedBy] = "percona-server-mysql-operator" |
There was a problem hiding this comment.
This change will cause a lot of changes, including changing a lot of compare files. If we want to follow the recommended labels convention, I would like to do this in another PR as part of this task: https://perconadev.atlassian.net/browse/K8SPS-442
| mysql.percona.com/version: v0.10.0 | ||
| app.kubernetes.io/name: percona-server | ||
| app.kubernetes.io/part-of: percona-server | ||
| app.kubernetes.io/version: v0.10.0 |
There was a problem hiding this comment.
@pooknull please use the same approach as we did for PSMDBO
labels:
app.kubernetes.io/component: crd
app.kubernetes.io/name: percona-server-mongodb
app.kubernetes.io/part-of: percona-server-mongodb-operator
app.kubernetes.io/version: v1.21.0
| LabelPartOf = kubernetesPrefix + "part-of" | ||
| LabelComponent = kubernetesPrefix + "component" | ||
|
|
||
| LabelOperatorVersion = kubernetesPrefix + "version" |
There was a problem hiding this comment.
I think that this const is only used in unit tests, maybe because we are adding the version to the crd directory through the generate command. If we don't use it actually somewhere else other than tests maybe it is better to move it in the test file and make it non-exported, or remove it completely and have a constant inside the test function and keep it scoped.
Ege fixed it under cfa2781 |


https://perconadev.atlassian.net/browse/K8SPS-426
DESCRIPTION
This PR replaces
mysql.percona.com/versionlabel from #850 withapp.kubernetes.io/version.Also this PR adds the following labels to the
crd.yaml:CHECKLIST
Jira
Needs Doc) and QA (Needs QA)?Tests
Config/Logging/Testability