Open
Conversation
rjgoyln
requested review from
bugraoz93,
hussein-awala,
jedcunningham and
jscheffl
as code owners
plaes
reviewed
Mar 24, 2026
chart/values.yaml
Outdated
| # Add custom annotations to the api secret | ||
| apiSecretAnnotations: {} | ||
| # Must contain an 'api-secret-key' key (suggested: random 32-char string). | ||
| # Note: Values in K8s Secrets must be Base64 encoded. |
There was a problem hiding this comment.
This is somewhat confusing. It kinda tells me that I should base64 the value before adding it to secret...
kubectl create --dry-run=client secret generic \
admin --from-literal=api-secret-key=$(echo -n really-secret | base64) -oyamlAnd k8s re-encodes it in base64:
data:
api-secret-key: Y21WaGJHeDVMWE5sWTNKbGRBPT0=It probably should mention to create a "generic" secret within data field, instead of stringData.
Contributor
Author
There was a problem hiding this comment.
OK, got it. Thank you so much🙏🙏.
I’ve removed the comments that might cause confusion. Please let me know if there’s anything else I should change.
potiuk
added
the
ready for maintainer review
rjgoyln
force-pushed
the
Include_key_names
branch
from
888870e to
04c954a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds missing documentation for several secret name parameters in values.yaml. These parameters were previously undocumented or lacked specific details regarding their required internal Kubernetes Secret keys and fallback behaviors.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.