Hook prefect-kubernetes
into setting framework
#15888
Merged
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.
This PR creates settings models for
prefect-kubernetes
that allow settings forprefect-kubernetes
to be set in via the same methods as coreprefect
. This PR establishes a pattern for integrations settings to be located under theintegrations
table in TOML files or use thePREFECT_INTEGRATIONS_
prefix for environment variable based sources.For example, you can toggle the TCP keepalive setting via a
prefect.toml
file like this:or via a
pyproject.toml
like this:or via an environment variables like this:
This PR also adds a new setting to be able to specify an existing k8s secret to give to created jobs for the Prefect API key. The plan is to add this to the k8s worker helm chart since that chart create a secret for the Prefect API key by default.
This will need to be merged after the next release because it relies on some unreleased utilities.
Closes #7185