Allow user to specify custom secrets to be mounted on Feast Serving and Feast Core pods #1127
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.
…
Signed-off-by: Khor Shu Heng [email protected]
What this PR does / why we need it:
Currently, users has no way to mount existing Kubernetes secrets to Feast services. One of the consequences of this is that Feast Core and Feast Serving would not be able to use GCP authentication, since there is no way to set up Google Application Credential.
This PR adds a new helm values called
secrets
, which the user can provide the list of kubernetes secrets to be mounted. They can then use envoverride variable to setup the credentials.Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: