Skip to content

Allow user to specify custom secrets to be mounted on Feast Serving and Feast Core pods - #1127

Merged
feast-ci-bot merged 1 commit into
feast-dev:masterfrom
khorshuheng:generic-secret
Nov 3, 2020
Merged

Allow user to specify custom secrets to be mounted on Feast Serving and Feast Core pods#1127
feast-ci-bot merged 1 commit into
feast-dev:masterfrom
khorshuheng:generic-secret

Conversation

@khorshuheng

Copy link
Copy Markdown
Collaborator

Signed-off-by: Khor Shu Heng khor.heng@gojek.com

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?:


…nd Feast Core pods

Signed-off-by: Khor Shu Heng <khor.heng@gojek.com>
@feast-ci-bot

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: khorshuheng, pyalex

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@pyalex

pyalex commented Nov 3, 2020

Copy link
Copy Markdown
Collaborator

/lgtm

@pyalex

pyalex commented Nov 3, 2020

Copy link
Copy Markdown
Collaborator

/test test-end-to-end-gcp

@feast-ci-bot
feast-ci-bot merged commit f67fe7a into feast-dev:master Nov 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants