[kong] migrate controller to envvar-based configuration #99
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.
What this PR does / why we need it:
env
block generation to the dict-based system used by the Kong container.kong_admin_tls_skip_verify
default and examplekong_admin_token
in values.yaml.Special notes for your reviewer:
POD_NAMESPACE
andPOD_NAME
remain outside the new system (they're still part of thekong.controller-container
template). Users cannot override them (user variables all receive theCONTROLLER_
prefix) and we'd need an additional (albeit simple) template to handle fieldRefs, so I think it's reasonable to omit them.kong_admin_tls_skip_verify
is now a user-set variable with a default in values.yaml, it also has a default inside the template. This is to account for users with an existing values.yaml that specifiesenv: {}
.Checklist
next
branch and targetsnext
, notmaster
[kong]
)