Failed sync attempt to 0af37aa48da698b59b60e49f42b7ab777c20e89c: one or more objects failed to apply, reason: Deployment.apps "airbyte-worker" is invalid: spec.template.spec.containers[0].env[26].valueFrom: Invalid value: "": must specify one of:

fieldRef

,

resourceFieldRef

,

configMapKeyRef

or

secretKeyRef

,Deployment.apps "airbyte-workload-api-server" is invalid: spec.template.spec.containers[0].env[15].valueFrom: Invalid value: "": must specify one of:

fieldRef

,

resourceFieldRef

,

configMapKeyRef

or

secretKeyRef

The error message you are seeing:

Invalid value: "": must specify one of: `fieldRef`, `resourceFieldRef`, `configMapKeyRef` or `secretKeyRef`

indicates that an environment variable in your Airbyte deployment is being defined with a

valueFrom

field, but none of the required subfields (

fieldRef

,

resourceFieldRef

,

configMapKeyRef

, or

secretKeyRef

) are specified. This typically happens when a value is missing or misconfigured in your

values.yaml

or referenced secrets/configmaps. This issue has been reported by other users and is often caused by: - A missing or empty value for a secret or config map key referenced in your Helm values. - Incorrect or missing configuration for secret names or keys, especially when using S3 or other external storage backends. - Not providing required values such as

global.secretsManager.secretsManagerSecretName

or using the wrong key names in your secrets. How to resolve: 1. Check your

values.yaml

: Ensure that all environment variables that use

valueFrom

have the correct references and that the referenced secrets/configmaps and keys exist and are not empty. 2. For S3 or external storage: If you are using S3, make sure you are using the correct key names in your secret. For example, if your deployment expects

AWS_ACCESS_KEY_ID

and

AWS_SECRET_ACCESS_KEY

, your secret should use those exact keys, not custom ones like

s3-access-key-id

unless you have customized the chart templates accordingly. See this example for reference:

yaml     apiVersion: v1     kind: Secret     metadata:       name: airbyte-airbyte-secrets       namespace: dev     data:       AWS_ACCESS_KEY_ID: <keyid>       AWS_SECRET_ACCESS_KEY: <key-sec>

And in your deployment:

yaml     - name: AWS_ACCESS_KEY_ID       valueFrom:         secretKeyRef:           name: airbyte-airbyte-secrets           key: AWS_ACCESS_KEY_ID     - name: AWS_SECRET_ACCESS_KEY       valueFrom:         secretKeyRef:           name: airbyte-airbyte-secrets           key: AWS_SECRET_ACCESS_KEY

[Issue with S3 secret keys](https://github.com/airbytehq/airbyte/issues/48008) 3. Check for missing secret names: If you see errors like

valueFrom.secretKeyRef.name: Invalid value: ""

, it means the secret name is missing. For AWS Secret Manager, for example, you must set

global.secretsManager.secretsManagerSecretName

in your values file if you are using that integration. [Getting valueFrom.secretKeyRef.name invalid value](https://github.com/airbytehq/airbyte/discussions/45386) 4. Review your environment variable definitions: Make sure you are not leaving any environment variable definitions incomplete. Every

valueFrom

must have a valid subfield. If you continue to have issues, please share the relevant parts of your

values.yaml

and the secrets you have created (with sensitive data redacted), as this will help pinpoint the misconfiguration. If you are following the documentation and still encountering this, it may be due to a mismatch between the expected and actual secret/configmap keys, or a missing required value in your configuration. Let me know if you need help reviewing your specific configuration!