-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Samples - Moved secret application to the pipeline definition #536
Samples - Moved secret application to the pipeline definition #536
Conversation
4258b02
to
83feffd
Compare
just wondering why this is better. |
/lgtm |
The component definitions should be shareable/portable. Adding secrets to the definitions ties them to a particular installation so at least the components are portable/shareable. In future we can try to move this to even higher level (pipeline level or cluster level), so that the pipeline can also be portable. |
The implementation of the component depends on a gcp secret. It's better to let component author to declare it. Ideally, user just need to setup the secrete in their pipeline service once and no need to configure any secret in their pipelines. |
That's true for some components (e.g. CMLE), but most of other components can actually work on files.
That's the goal, yes. |
I think it is a good idea since the component code is supposed to be "binary" and not modifiable. Setting credential in component code causes it less portable. I though of doing this when we have a packaging story (yaml). |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Ark-kun The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
1 similar comment
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Ark-kun The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
One implementation option is that we let component author to put a secret hint in the component spec and it pass through as a label on pod. We can leverage podpreset to mount the GCP secret volume by matching label. |
P.S. How did
samples/tfx/taxi-cab-classification-pipeline.py
work if theconfusion_matrix_op
did not use a secret?This change is