Details
-
Bug
-
Status: Done
-
Medium
-
Resolution: Fixed
-
1.9.0, 1.11.0
-
None
-
None
-
Yes
Description
It's possible to update labels in 1.7.0, but in 1.9.0 and 1.11.0
./anydbver deploy k3s node1 k3s-master:default node2 k3s-master:default node3 k3s-master:default default k8s-mongo:1.11.0 [[email protected] ~]# vi percona-server-mongodb-operator/deploy/cr.yaml [[email protected] ~]# kubectl get pod --show-labels my-cluster-name-rs0-0 NAME READY STATUS RESTARTS AGE LABELS my-cluster-name-rs0-0 2/2 Running 0 7m20s app.kubernetes.io/component=mongod,app.kubernetes.io/instance=my-cluster-name,app.kubernetes.io/managed-by=percona-server-mongodb-operator,app.kubernetes.io/name=percona-server-mongodb,app.kubernetes.io/part-of=percona-server-mongodb,app.kubernetes.io/replset=rs0,controller-revision-hash=my-cluster-name-rs0-7f9b4cffd8,statefulset.kubernetes.io/pod-name=my-cluster-name-rs0-0 [[email protected] ~]# kubectl apply -f percona-server-mongodb-operator/deploy/cr.yaml perconaservermongodb.psmdb.percona.com/my-cluster-name configured # git diff deploy/cr.yaml diff --git a/deploy/cr.yaml b/deploy/cr.yaml index ee15c5a..8ef8321 100644 --- a/deploy/cr.yaml +++ b/deploy/cr.yaml @@ -81,8 +81,8 @@ spec: # priorityClassName: high-priority # annotations: # iam.amazonaws.com/role: role-arn -# labels: -# rack: rack-22 + labels: + rack: rack-22 # nodeSelector: # disktype: ssd # livenessProbe: [[email protected] ~]# kubectl get pod --show-labels my-cluster-name-rs0-0 NAME READY STATUS RESTARTS AGE LABELS my-cluster-name-rs0-0 2/2 Running 0 8m20s app.kubernetes.io/component=mongod,app.kubernetes.io/instance=my-cluster-name,app.kubernetes.io/managed-by=percona-server-mongodb-operator,app.kubernetes.io/name=percona-server-mongodb,app.kubernetes.io/part-of=percona-server-mongodb,app.kubernetes.io/replset=rs0,controller-revision-hash=my-cluster-name-rs0-7f9b4cffd8,statefulset.kubernetes.io/pod-name=my-cluster-name-rs0-0