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

Use latest katib images to deploy katib #682

Merged
merged 1 commit into from Jul 12, 2019
Merged

Use latest katib images to deploy katib #682

merged 1 commit into from Jul 12, 2019

Conversation

hougangliu
Copy link
Member

@hougangliu hougangliu commented Jul 11, 2019

After this patch, user can install katib individually (not install kubeflow) with latest images by deploy.sh.


This change is Reviewable

@hougangliu
Copy link
Member Author

@@ -23,7 +23,7 @@ data:
serviceAccountName: metrics-collector
containers:
- name: {{.WorkerID}}
image: katib/metrics-collector
image: gcr.io/kubeflow-images-public/katib/v1alpha1/metrics-collector
Copy link
Member

Choose a reason for hiding this comment

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

@johnugeorge Do we have the repository in dockerhub? If not I think the PR LGTM

Copy link
Member Author

Choose a reason for hiding this comment

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

AFAIK, we hasn't maintained katib images in dockerhub for a long time. some users try to install katib by deploy.sh, but Katib cannot work well for the images are too old

Copy link
Member

Choose a reason for hiding this comment

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

I think, it is better to keep single source of truth. Since our images are built in gcr, this PR looks good to me than maintaining in two different repos.
One related question is, should we point to release tagged image than picking up the latest image from master? Release image can be updated in the manifests after every release. eg: 0.6 Else, users might see new untested features and different behavior from the docs which will be confusing to them.

Copy link
Member Author

Choose a reason for hiding this comment

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

@johnugeorge, Agree with you. But I think for master branch, we can just keep latest images which keep consistent with master source code. For a released branch, we should modify the images with released version tag.

Copy link
Member

Choose a reason for hiding this comment

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

@hougangliu But, won't users deploy Katib from master branch always?

Copy link
Member Author

Choose a reason for hiding this comment

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

we can doc about what images the installer will use. In fact, for end user, I think he should install katib by kubeflow kfctl, which always installs released images. For deploy.sh here, it is prepared for developers, who're likely to test how current code runs.

Copy link
Member

Choose a reason for hiding this comment

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

SGTM. If developers need to use our scripts to deploy(without Katib), we can provide link to the manifests of last deployed branch. We need to add this to README

@hougangliu
Copy link
Member Author

/test kubeflow-katib-presubmit

@johnugeorge
Copy link
Member

test env is broken in all repos now.

@johnugeorge
Copy link
Member

/lgtm

@hougangliu
Copy link
Member Author

/approve

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hougangliu

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 02c3528 into kubeflow:master Jul 12, 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.

None yet

4 participants