-
Notifications
You must be signed in to change notification settings - Fork 17.3k
document missing secret name keys #64135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -498,19 +498,14 @@ extraEnvFrom: ~ | |
|
|
||
| # Airflow database & redis config | ||
| data: | ||
| # If secret names are provided, use those secrets | ||
| # These secrets must be created manually, eg: | ||
| # | ||
| # kind: Secret | ||
| # apiVersion: v1 | ||
| # metadata: | ||
| # name: custom-airflow-metadata-secret | ||
| # type: Opaque | ||
| # data: | ||
| # connection: base64_encoded_connection_string | ||
|
|
||
| # Must contain a 'connection' key (e.g., postgresql://user:pass@host:5432/db). | ||
| # Optional: 'kedaConnection'. Note: URL-encode special characters in passwords. | ||
| metadataSecretName: ~ | ||
|
|
||
| # Must contain a 'connection' key. If not provided, it falls back to 'metadataSecretName'. | ||
| resultBackendSecretName: ~ | ||
|
|
||
| # Must contain a 'connection' key (e.g., redis://:pass@host:6379/0). | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ...and also I'd not repeat it here but propose to add this to the note that the key is relevant for all options below. |
||
| brokerUrlSecretName: ~ | ||
|
|
||
| # Otherwise pass connection values in | ||
|
|
@@ -545,6 +540,10 @@ data: | |
| # Fernet key settings | ||
| # Note: fernetKey can only be set during install, not upgrade | ||
| fernetKey: ~ | ||
| # The Secret MUST contain a 'fernet-key' key. | ||
| # | ||
| # To handle rotation, provide multiple comma-separated keys in the Secret. | ||
| # New values are encrypted with the first key; decryption is attempted with all keys. | ||
| fernetKeySecretName: ~ | ||
| # Add custom annotations to the fernet key secret | ||
| fernetKeySecretAnnotations: {} | ||
|
|
@@ -553,18 +552,21 @@ fernetKeySecretAnnotations: {} | |
| apiSecretKey: ~ | ||
| # Add custom annotations to the api secret | ||
| apiSecretAnnotations: {} | ||
| # Must contain an 'api-secret-key' key (suggested: random 32-char string). | ||
| apiSecretKeySecretName: ~ | ||
|
|
||
| # Secret key used to encode and decode JWTs: `[api_auth] jwt_secret` in airflow.cfg | ||
| jwtSecret: ~ | ||
| # Add custom annotations to the JWT secret | ||
| jwtSecretAnnotations: {} | ||
| # Must contain a 'jwt-secret' key (suggested: random 32-char string). | ||
| jwtSecretName: ~ | ||
|
|
||
| # Flask secret key for Airflow <3 Webserver: `[webserver] secret_key` in airflow.cfg | ||
| webserverSecretKey: ~ | ||
| # Add custom annotations to the webserver secret | ||
| webserverSecretAnnotations: {} | ||
| # Must contain a 'webserver-secret-key' key (suggested: random 32-char string). | ||
| webserverSecretKeySecretName: ~ | ||
|
|
||
| # In order to use kerberos you need to create secret containing the keytab file | ||
|
|
@@ -2777,6 +2779,7 @@ flower: | |
| annotations: {} | ||
|
|
||
| # A secret containing the connection | ||
| # The Secret MUST contain a 'basicAuth' key (formatted as 'username:password') | ||
| secretName: ~ | ||
| # Add custom annotations to the flower secret | ||
| secretAnnotations: {} | ||
|
|
||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if and why your description is now better than the example before. The example before which you now are removing had an example. Yes it was not mentioning that the
connectionkey is needed.I'd favor keeping the example and marking the note that key(s) are needed.