Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-784

[DOCUMENT] quarkus.kubernetes-config.secrets.enabled takes precedence over quarkus.kubernetes-config.enabled

XMLWordPrintable

    • False
    • False
    • Documentation (Ref Guide, User Guide, etc.), Release Notes
    • +
    • Undefined
    • Hide

      1. Check out https://github.com/quarkus-qe/quarkus-openshift-test-suite
      2. Remove the workaround.
      3. mvn clean test -pl config-secret/api-server/ -Dquarkus-core-only The unit test will fail as it is attempting to reach Kubernetes server it should not be.
      4. mvn clean test -pl config-secret/api-server/ -Dquarkus-core-only -Dversion.quarkus=1.7.2.Final The unit test passes.

      Show
      1. Check out https://github.com/quarkus-qe/quarkus-openshift-test-suite 2. Remove the workaround . 3. mvn clean test -pl config-secret/api-server/ -Dquarkus-core-only The unit test will fail as it is attempting to reach Kubernetes server it should not be. 4. mvn clean test -pl config-secret/api-server/ -Dquarkus-core-only -Dversion.quarkus=1.7.2.Final The unit test passes.
    • ---

      quarkus.kubernetes-config.secrets.enabled takes precedence over quarkus.kubernetes-config.enabled. When quarkus.kubernetes-config.secrets.enabled=true and quarkus.kubernetes-config.enabled=false, Quarkus application will still try to get configuration from secrets.

      This is a change of behaviour compared to Quarkus 1.7.

      Expected behaviour
      RHBQ 1.7 behaviour - when quarkus.kubernetes-config.enabled=false, Quarkus app should not be attempting to get configuration from Kubernetes API server.

      Actual behavior
      When quarkus.kubernetes-config.enabled=false and quarkus.kubernetes-config.secrets.enabled=true, Quarkus app attempts to get configuration from secrets from Kubernetes API server.

              ssitani Stefan Sitani (Inactive)
              mjurc@redhat.com Michal Jurc
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: