wave-k8s / wave

Kubernetes configuration tracking controller
Apache License 2.0
646 stars 82 forks source link

changes to projected volumes not detected properly #127

Closed sdahlbac closed 1 month ago

sdahlbac commented 1 year ago
    volumes:
      - configMap:
          defaultMode: 420
          name: kafka-jmx-configmap
          optional: false
        name: jmx-config
      - name: tls-conf
        projected:
          defaultMode: 420
          sources:
          - secret:
              name: kafka-secret
              optional: false
          - secret:
              items:
              - key: keystore.jks
                path: kafka-0-keystore.jks
              - key: truststore.jks
                path: truststore.jks
              name: kafka-0-tls-secret
              optional: false
          - secret:
              items:
              - key: keystore.jks
                path: kafka-1-keystore.jks
              name: kafka-1-tls-secret
              optional: false
          - secret:
              items:
              - key: keystore.jks
                path: kafka-2-keystore.jks
              name: kafka-2-tls-secret
              optional: false

If I trigger a certmanager renewal of a certificate, e.g. the kafka-0-tls-secret gets updated properly, but this is not detected by wave?

sdahlbac commented 1 year ago

For now, I went with https://github.com/stakater/Reloader (with --reload-strategy=annotations)

github-actions[bot] commented 1 year ago

This issue has been inactive for 60 days. If the issue is still relevant please comment to re-activate the issue. If no action is taken within 7 days, the issue will be marked closed.

sdahlbac commented 1 year ago

This issue is still relevant, but it seems the project might be dead