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.
Fixes: #368 #283 #370
This PR adresses several issues.
.Values.nautobot.secretKey
to be specified but it also introduces a new structure named.Values.nautobot.django.*
which takes priority. It still allows the user to specify a key in the configuration or, alternatively, to pass in a reference to an existing secret.All these references can use a user-supplied secret and user-supplied key if necessary but do fall back to the defaults when necessary.
If no references or secret values are supplied the bitnami common chart is used to generate them and populate these secrets.
The superuser and secret key values are by default added to the existing *-env secret. But if referenced individually they are added as independet env variables to the relevant pods. If all of these variables are referenced to an existing secret the *-env secret becomes empty. However it is still created without any data to avoid broken secret references in the other objects.
If all of these features are used together it allows the user to not specify any secrets in the values.yaml file.