Details

    Description

      CR updated from:

       

      .
      .
        proxysql:
          affinity:
            antiAffinityTopologyKey: kubernetes.io/hostname
      .
      .

      to:

       

        proxysql:
          affinity:
            antiAffinityTopologyKey: kubernetes.io/hostname
          annotations:
            backup.velero.io/backup-volumes-excludes: proxydata
      

       

       

      The operator now update the proxysql sts and trigger a rollout of the proxysql pods.

      This is not happening.

      Noticed the same behavior for a change like:

       

      // code placeholder
        pxc:
          affinity:
            antiAffinityTopologyKey: kubernetes.io/hostname
      

      to:

        pxc:
          affinity:
            antiAffinityTopologyKey: kubernetes.io/hostname
          configuration: |
            [mysqld]
            sql_mode=""
      

      Config map was updated correctly but no rollout was triggered for the pxc pods, so mysql did not notice the config change.

      Thanks,

      Thomas

       

       

      Attachments

        Activity

          People

            bulat.zamalutdinov Bulat Zamalutdinov (Inactive)
            bitsbeats BitsBeats
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 week, 1 day, 7 hours
                1w 1d 7h

                Smart Checklist