You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What did you do to encounter the bug?
We first deploy the MongoDB cluster with a toleration sepecified.
Then we tried to remove the toleration from the statefulSet/pods, by deleting the toleration in spec.statefulSet.template.spec.tolerations.
Then we realized that the operator is unable to remove the toleration.
Steps to reproduce the behavior:
Deploy the MongoDB cluster with spec:
apiVersion: mongodbcommunity.mongodb.com/v1kind: MongoDBCommunitymetadata:
namespace: mongodbname: test-clusterspec:
automationConfig:
processes:
- disabled: falsename: test-cluster-1members: 3type: ReplicaSetversion: "4.4.0"security:
authentication:
modes: ["SCRAM"]users:
- name: my-userdb: adminpasswordSecretRef: # a reference to the secret that will be used to generate the user's passwordname: my-user-passwordroles:
- name: clusterAdmindb: admin
- name: userAdminAnyDatabasedb: adminscramCredentialsSecretName: my-scramstatefulSet:
spec:
template:
spec:
containers:
- name: mongodresources:
limits:
cpu: '1'memory: 1000Mrequests:
cpu: '1'memory: 1000M
- name: mongodb-agentresources:
limits:
cpu: '1'memory: 1000Mrequests:
cpu: '1'memory: 1000Mtolerations:
- effect: NoSchedulekey: test-keyoperator: Equalvalue: test-value
Remove the toleration from the spec.statefulSet.template.spec.tolerations:
apiVersion: mongodbcommunity.mongodb.com/v1kind: MongoDBCommunitymetadata:
namespace: mongodbname: test-clusterspec:
automationConfig:
processes:
- disabled: falsename: test-cluster-1members: 3type: ReplicaSetversion: "4.4.0"security:
authentication:
modes: ["SCRAM"]users:
- name: my-userdb: adminpasswordSecretRef: # a reference to the secret that will be used to generate the user's passwordname: my-user-passwordroles:
- name: clusterAdmindb: admin
- name: userAdminAnyDatabasedb: adminscramCredentialsSecretName: my-scramstatefulSet:
spec:
template:
spec:
containers:
- name: mongodresources:
limits:
cpu: '1'memory: 1000Mrequests:
cpu: '1'memory: 1000M
- name: mongodb-agentresources:
limits:
cpu: '1'memory: 1000Mrequests:
cpu: '1'memory: 1000M
What did you expect?
The operator should be able to remove the toleration from the statefulset as specified in the CR.
What happened instead?
The toleration is left on the statefulset and cannot be removed
The text was updated successfully, but these errors were encountered:
tylergu
changed the title
mongodb-operator does not remove the toleration from statefulset/pods
mongodb-operator cannot remove tolerations from statefulset/pods as specified in CR
Mar 29, 2023
What did you do to encounter the bug?
We first deploy the MongoDB cluster with a toleration sepecified.
Then we tried to remove the toleration from the statefulSet/pods, by deleting the toleration in
spec.statefulSet.template.spec.tolerations
.Then we realized that the operator is unable to remove the toleration.
Steps to reproduce the behavior:
spec.statefulSet.template.spec.tolerations
:What did you expect?
The operator should be able to remove the toleration from the statefulset as specified in the CR.
What happened instead?
The toleration is left on the statefulset and cannot be removed
Operator Information
0.7.4
4.4.0
Kubernetes Cluster Information
kubectl version --short --output=yaml
The text was updated successfully, but these errors were encountered: