Bug #111534 MySQL Operator - dont update router podspec

• Submitted: 22 Jun 2023 10:09
• Modified: 18 Jan 2024 15:26
• Reporter: Carlos Abrantes
• Status: Won't fix
• Category: MySQL Operator
• Severity: S2 (Serious)
• OS: Any
• CPU Architecture: Any

[22 Jun 2023 10:09] Carlos Abrantes

Description:
After deploying MySQL Operator and MySQL InnoDBCluster i tried to update affinity rules via podspec,

      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: layer/router
                operator: Exists

to

    affinity:
      nodeAffinity:
        requiredDuringSchedulingIgnoredDuringExecution:
          nodeSelectorTerms:
          - matchExpressions:
            - key: layer/router
              operator: Exists
      podAntiAffinity:
        requiredDuringSchedulingIgnoredDuringExecution:
        - labelSelector:
            matchExpressions:
            - key: component
              operator: In
              values:
              - mysqlrouter
          topologyKey: kubernetes.io/hostname

or remove at all the podspec.

Nothing is updated, Operator don't show any logs, router deployment also is not update.

Version:
community-operator:8.0.33-2.0.10
community-server:8.0.33
community-router:8.0.33

apiVersion: v2
appVersion: 8.0.33
description: MySQL InnoDB Cluster Helm Chart for deploying MySQL InnoDB Cluster in Kubernetes
icon: https://labs.mysql.com/common/themes/sakila/favicon.ico
name: mysql-innodbcluster
type: application
version: 2.0.10

How to repeat:

1 - Deploy Operator, MySQL Cluster.
2 - Change the helm values.
3 - run helm upgrade with the new values

Suggested fix:

Router deployment should be updated.

[26 Jun 2023 3:15] MySQL Verification Team

Thanks for the report

[27 Jun 2023 18:39] Carlos Abrantes

Assuming that its a bug that will be fixed in the future, is there any workaround that can be applied?

[13 Jul 2023 23:08] Carlos Abrantes

Hi,

Can you confirm if for changing the podspec, we need to delete the existing InnoDBCluster and add it again with the updated value?

Thanks,
Carlos

[18 Jan 2024 15:26] Johannes Schlüter

Posted by developer:
 
Duplicate of bug #34973960