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

pipeline-lite/metadata: Update readme #2093

Conversation

dushyanthsc
Copy link
Contributor

@dushyanthsc dushyanthsc commented Sep 12, 2019

Change adds necessary instructions required to configure Kubernetes secretes required for metaata server deployment in Pipeline Lite deployments.


This change is Reviewable

@dushyanthsc
Copy link
Contributor Author

/test kubeflow-pipeline-e2e-test
/test kubeflow-pipeline-sample-test

required secret object.

```
kubectl create secret generic mysql-credential --namespace <your-namespace> --from-literal=username=<your-mysql-username> --from-literal=password=<your-mysql-password>
Copy link
Contributor

Choose a reason for hiding this comment

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

What's the default username and password as used by APIServer? Is it still root and empty password? If so, let's mention that here, and tell the user to create it with these defaults.

Should we just create this secret as part of the deployment script? This should be the default, and we can call out that this is what needs to be changed by the user if re-using an existing DB (e.g. CloudSQL).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The default is still "root" and empty password. Will update the doc to reflect this.

By deployment script you mean for Marketplace? I am sure if lite deployment has one?

Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry, I mean this pipeline-lite deployment, not marketplace.

Essentially, since the default user and pass is also used by APIServer, so why not create a secret that uses the same settings?

/cc @IronPan

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I like the idea, essential create a Secret object via yaml files and then use that across other components. Let me update the PR with that change.

@neuromage
Copy link
Contributor

/assign @neuromage

@Ark-kun
Copy link
Contributor

Ark-kun commented Sep 17, 2019

/retest

@dushyanthsc dushyanthsc force-pushed the dushyanthsc/pipelines-lite-documentation branch from c6477fa to 595cc07 Compare September 20, 2019 23:49
Change to create mysql credential K8 object as part of deployment
@dushyanthsc dushyanthsc force-pushed the dushyanthsc/pipelines-lite-documentation branch from 595cc07 to abaf129 Compare September 20, 2019 23:52
@neuromage
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neuromage

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

@k8s-ci-robot k8s-ci-robot merged commit ab8f5ed into kubeflow:master Sep 21, 2019
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