Skip to content
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

[KFP v2] Fix the S3 secret name is hardcoded in the KFP library. #1030

Open
wants to merge 4 commits into
base: dev
Choose a base branch
from

Conversation

revit13
Copy link
Collaborator

@revit13 revit13 commented Feb 10, 2025

Why are these changes needed?

FIX - Due to kubeflow/pipelines#10914, we cannot provide secret names as pipeline arguments, so we agreed to a workaround that the secret name will be hard-coded.
The secret names should be in pipeline, so users will be able to overwrite them. Currently it is in the library, so users cannot change it.

Related issue number (if any).

#985

@revit13 revit13 requested a review from roytman February 10, 2025 07:42
# FIXME: Due to kubeflow/pipelines#10914, secret names cannot be provided as pipeline arguments.
# As a workaround, the secret name is hard coded.
env2key = ComponentUtils.set_secret_key_to_env()
kubernetes.use_secret_as_env(task=execute_job, secret_name="s3-secret", secret_key_to_env=env2key)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest defining a constant at the start of the file and using it here. It will simplify for users to update it.

Signed-off-by: Revital Sur <[email protected]>
Signed-off-by: Revital Sur <[email protected]>
@roytman roytman requested a review from touma-I February 10, 2025 19:59
Signed-off-by: Revital Sur <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants