Eduardo Ferreira
11/26/2025, 1:10 PMkapa.ai
11/26/2025, 1:11 PM.Values.global.secrets in your values.yaml is not a map/object (key–value structure), but some other type (often a string, boolean, or empty interface), and the Helm template for the workload-api-server expects a map. In the provided knowledge sources, there is no explicit documentation of the workload-api-server/templates/secrets.yaml or an example of the global.secrets structure for chart 1.8.5, so I can't tell you the exact expected schema. The docs only show: - How to precreate a Kubernetes secret called airbyte-config-secrets and reference it in values.yaml via global.secretsManager.secretName (for external secret managers). [[Preconfiguring secrets](https://docs.airbyte.com/platform/1.8/deploying-airbyte/creating-secrets); [Secret manager values](https://docs.airbyte.com/platform/1.8/deploying-airbyte/integrations/secrets#values)] - Examples of global.secretsManager configuration for AWS/GCP/Azure, but not global.secrets itself. [[Secret manager values](https://docs.airbyte.com/platform/1.8/deploying-airbyte/integrations/secrets#values)] Given that, all I can say confidently is: 1. In your values.yaml, locate any definition of global.secrets. 2. Ensure it is either: - Removed (if not needed by your setup), or - Defined as a YAML map, for example: yaml global: secrets: someKey: someValue anotherKey: anotherValue 3. If you copied global.secrets from older docs, examples, or another environment, verify that the structure matches what the 1.8.5 chart expects. Unfortunately, the available documentation does not specify that structure. Because the knowledge sources don’t include the 1.8.5 workload-api-server chart template or a reference for global.secrets, I’m unable to provide an exact corrective values.yaml snippet beyond the type constraint (it must be a map/object).Eduardo Ferreira
11/26/2025, 1:12 PMkapa.ai
11/26/2025, 1:12 PMkapa.ai
11/26/2025, 1:13 PM.Values.global.secrets, so Helm still “sees” that key in your effective values, even if you’ve deleted it from your local values.yaml. From the docs and issues you shared, there are two relevant points: 1. For Helm chart v2 (including 1.8.x), secrets are meant to be handled via: - A pre-created Kubernetes secret like airbyte-config-secrets [[Preconfiguring secrets](https://docs.airbyte.com/platform/1.8/deploying-airbyte/creating-secrets)], and - The global.secretsManager block (not global.secrets). [[Chart v2 community](https://docs.airbyte.com/platform/1.8/deploying-airbyte/chart-v2-community#update-your-valuesyaml-file)] 2. When upgrading charts, using an old/full values file can cause exactly this sort of schema mismatch. The recommended pattern is to start from a minimal values file and add back only the overrides you really need. [[Helm upgrade issue](https://github.com/airbytehq/airbyte/issues/49843)] Given that, most likely causes are: - global.secrets is still present via: - Another values file passed with `-f`/`--values`, or - Values stored with the release and merged via --reuse-values. - Or the chart version you’re upgrading from left global.secrets in the stored release values, and Helm is merging those with your new ones. To isolate this, try: 1. Upgrade without reusing old values, passing only a minimal file: bash helm upgrade airbyte airbyte/airbyte \ --version 1.8.5 \ --namespace <your-namespace> \ -f minimal-values.yaml \ --reset-values Where minimal-values.yaml contains only the essentials, e.g.: yaml global: edition: community airbyteUrl: "https://your-airbyte-url" # If using external DB: # global: # database: # secretName: "airbyte-config-secrets" # host: "..." # port: 5432 # name: "..." # user: "..." # password: "..." # # postgresql: # enabled: false This follows the documented recommendation to start from a basic v2 values.yaml and map your customizations gradually. [[Chart v2 upgrade](https://docs.airbyte.com/platform/1.8/deploying-airbyte/chart-v2-community#update-your-valuesyaml-file); [Helm upgrade issue](https://github.com/airbytehq/airbyte/issues/49843)] 2. Check the current stored values to confirm if global.secrets is still present: bash helm get values airbyte -n <your-namespace> -a If global.secrets appears there, that explains why the template still fails. 3. Move any secret-related config to the documented places: - global.secretsManager for external secret managers. [[Chart v2 secretsManager](https://docs.airbyte.com/platform/1.8/deploying-airbyte/chart-v2-community#update-your-valuesyaml-file)] - A Kubernetes secret such as airbyte-config-secrets created before install/upgrade. [[Preconfiguring secrets](https://docs.airbyte.com/platform/1.8/deploying-airbyte/creating-secrets)] Because the provided docs and issues don’t include the exact workload-api-server/templates/secrets.yaml for 1.8.5, I can’t point to a specific line beyond confirming that it expects .Values.global.secrets to be a map. If, after a --reset-values upgrade with a minimal file, the error persists, it would indicate chart-internal behavior that isn’t documented in the sources you shared.