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

Improved the "IBM - Create kubernetes secret" component #1027

Conversation

Ark-kun
Copy link
Contributor

@Ark-kun Ark-kun commented Mar 23, 2019

Fixed the following issues:

  • Checking that every command finishes successfully (non-zero return code)
  • Fixed the path for the secret_name output (the program was producing variable paths different from the path in component.yaml)

This change is Reviewable

Fixed the following issues:
* Checking that every command finishes successfully (non-zero return code)
* Fixed the path for the secret_name output (the program was producing variable paths different from the path in component.yaml)
Copy link
Contributor

@animeshsingh animeshsingh left a comment

Choose a reason for hiding this comment

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

Thanks @Ark-kun. The idea here was to create a secret, and assign to kubernetes Apiserver, by using kubectl create secret command, rather than passing that as an input param for next component.

@Ark-kun
Copy link
Contributor Author

Ark-kun commented Mar 26, 2019

Thanks @Ark-kun. The idea here was to create a secret, and assign to kubernetes Apiserver, by using kubectl create secret command, rather than passing that as an input param for next component.

I understand that. I just noticed that the created secret can have inferred name which is deduced from the URL. Also having any output makes it easier to chain dependent tasks.

I can remove that output if you think it's not useful.

Are there any issues with other changes?

@animeshsingh
Copy link
Contributor

animeshsingh commented Mar 26, 2019

Thanks @Ark-kun - rest of the changes look good. I would say storing secrets in output file will still be a security hazerd, so best to remove that part.

@Ark-kun
Copy link
Contributor Author

Ark-kun commented Mar 26, 2019

I would say storing secrets in output file will still be a security hazard, so best to remove that part.

Just want to clarify: we're not storing/passing the actual secret. Just the secret name. Does this alleviate the concern?

@animeshsingh
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: animeshsingh

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Ark-kun
Copy link
Contributor Author

Ark-kun commented Apr 4, 2019

/test kubeflow-pipeline-e2e-test

@k8s-ci-robot k8s-ci-robot merged commit 4afa1fc into kubeflow:master Apr 4, 2019
@Ark-kun Ark-kun deleted the Improved-the-IBM---Create-kubernetes-secret-component branch April 6, 2019 06:48
@mpoqq
Copy link
Contributor

mpoqq commented Apr 26, 2019

Hi @Ark-kun, is it possible to update the docker image on docker hub ? Due to your changes the component.yaml pulls an old image and therefore this error config.py: error: unrecognized arguments: --output-secret-name-file /outputs/secret_name/data occurs.

@animeshsingh
Copy link
Contributor

animeshsingh commented Apr 26, 2019

we will take care of it @mpoqq

@mpoqq
Copy link
Contributor

mpoqq commented Apr 26, 2019

Thanks @animeshsingh, I think Watson Sample is also outdated.

@animeshsingh
Copy link
Contributor

@mpoqq the sample was updated recently, its dependent on the secret component and docker image though. key thing is even if the docker image doesn't go all the way, its able to create the secrets, so rest of the steps can continue. But we are going to update the image today. If you found any issue while running samples, please let us know

magdalenakuhn17 pushed a commit to magdalenakuhn17/pipelines that referenced this pull request Oct 22, 2023
Fixes variable parsing in `curl` request.
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this pull request Mar 11, 2024
)

* remove google and argo specific tests

* update removed links
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.

4 participants