Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

changing additionalVolumes does not trigger StatefulSet update #2761

Open
coopstah13 opened this issue Sep 12, 2024 · 0 comments
Open

changing additionalVolumes does not trigger StatefulSet update #2761

coopstah13 opened this issue Sep 12, 2024 · 0 comments

Comments

@coopstah13
Copy link

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using? 1.12.2
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? EKS, GKE, k3s
  • Are you running Postgres Operator in production? yes
  • Type of issue? Bug report

The fix performed for #1458 is incomplete. There is only a check for a difference of number of volumes, but not if the volumes themselves change.

For example, if you have

  additionalVolumes:
  - mountPath: /certs/minio
    name: minio-ca-cert
    targetContainers: []
    volumeSource:
      secret:
        secretName: minio-ca-cert

and you change it to (note the change to the secretName)

  additionalVolumes:
  - mountPath: /certs/minio
    name: minio-ca-cert
    targetContainers: []
    volumeSource:
      secret:
        secretName: minio-ca-cert-2

The operator does not pick up this change, because the volume count stays the same, and it only checks for differences in the volume mounts (which are the same in this case).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant