Add ephemeral package with environment variable registration #2857
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.
Change Overview
This PR introduces the
ephemeral
package meant to handle registering and applying ephemeral pod specific fields.The first use-case was to introduce FIPS related environment variables that need to be set on all ephemeral pods to ensure the crypto backend (OpenSSL in this case) is started with the FIPS provider enabled and fails otherwise.
The registration mechanism leaves it open to register conditional or static environment variables with the appropriate helper functions to help apply them. The only conditional environment variable helper at this point is the
OSEnvVar
which looks to see if the environment variable is set on the OS and applies it to the ephemeral pod if so. This usage is the main need for setting the FIPS environment variables since they're already present on the parent pod launching the ephemeral pods.All places that used the
kube.PodOptions
type had theephemeral.GlobalEnvVars()
function added which adds all registered environment variables to the pod.Two convenience functions
RegisterOSEnvVar
andRegisterStaticEnvVar
were added to help facilitate the registering of environment variables from packages which import this.Pull request type
Please check the type of change your PR introduces:
Issues
Test Plan