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

Katib ksonnet package #873

Merged
merged 6 commits into from
Jun 4, 2018
Merged

Katib ksonnet package #873

merged 6 commits into from
Jun 4, 2018

Conversation

lluunn
Copy link
Contributor

@lluunn lluunn commented May 25, 2018

Katib ksonnet components, following what are deploying in
https://github.com/kubeflow/katib/blob/master/scripts/deploy.sh

Fix kubeflow/katib#32


This change is Reviewable

@lluunn lluunn changed the title wip Katib ksonnet package Katib ksonnet package May 25, 2018
@lluunn
Copy link
Contributor Author

lluunn commented May 25, 2018

@gaocegege @YujiOshima @jlewi PTAL

@lluunn
Copy link
Contributor Author

lluunn commented May 29, 2018

/retest

3 similar comments
@lluunn
Copy link
Contributor Author

lluunn commented May 29, 2018

/retest

@lluunn
Copy link
Contributor Author

lluunn commented May 30, 2018

/retest

@lluunn
Copy link
Contributor Author

lluunn commented May 31, 2018

/retest

@lluunn
Copy link
Contributor Author

lluunn commented May 31, 2018

/cc @jlewi
/cc @YujiOshima

@jlewi
Copy link
Contributor

jlewi commented Jun 1, 2018

@lluunn Sorry for the delay. Just noticed ithis because it popped up in my dashboard finally. If you want me to review something /assign me. @ mentions will get buried in my inbox.

},
}, // dbDeployment

frontendService: {
Copy link
Contributor

Choose a reason for hiding this comment

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

Either in this PR or a follow on one we should add an Ambassador prefix to access the front end.

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 plan to do that in next PR. We have a different issue kubeflow/katib#88

value: "/katib",
},
],
image: "katib/katib-frontend",
Copy link
Contributor

Choose a reason for hiding this comment

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

Docker images should be exposed by parameters to make it easy to try new images.

},
],
image: "katib/katib-frontend",
imagePullPolicy: "Always",
Copy link
Contributor

Choose a reason for hiding this comment

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

Default imagePullPolicy should be IfNotPresent. Always is not good practice; we want to use the local cache.

},
}, // frontendDeployment

frontendIngress: {
Copy link
Contributor

Choose a reason for hiding this comment

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

Lets get rid of the ingress. Our networking story is that services are exposed via the Ambassador reverse proxy. I don't want to start creating ingress per service until we better understand the motivation for doing so.


// updatedParams uses the environment namespace if
// the namespace parameter is not explicitly set
local updatedParams = params {
Copy link
Contributor

Choose a reason for hiding this comment

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

You do not need this stanza. env should always contain environment because we are now require versions of ksonnet that ensure its true.

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 don't get it. Do you mean we should always use namespace from env?
I think the current logic is correct?

Copy link
Contributor

Choose a reason for hiding this comment

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

Correct you can just get namespace from env.
The logic is correct but unnecessary.

In earlier versions of ksonnet env wasn't available. So the way to get namespace was to make it available via a params.

A later version of ksonnet introduced env which contains namespace. But for backwards compatibility we still wanted to respect namespace in params. But we no longer need to do that.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

But then all components in one environment will have to have the same namespace?
Shouldn't we allow setting namespace per component?

Copy link
Contributor

Choose a reason for hiding this comment

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

Perhaps in the future. There's an implicit assumption that everything is already in the same namespace. So I wouldn't expect setting different namespaces would just work.

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 see

args: [
"modeldb-db",
],
image: "mitdbg/modeldb-backend:latest",
Copy link
Contributor

Choose a reason for hiding this comment

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

parameterize the image please

"-i",
"k-cluster.example.net",
],
image: "katib/vizier-core",
Copy link
Contributor

Choose a reason for hiding this comment

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

parameterize the image please

@jlewi
Copy link
Contributor

jlewi commented Jun 1, 2018

/assign jlewi
/assign @kunmingg

@lluunn
Copy link
Contributor Author

lluunn commented Jun 1, 2018

Thanks for reviewing, PTAL. Addressed the comments, except one question.

@lluunn
Copy link
Contributor Author

lluunn commented Jun 1, 2018

/retest

@jlewi
Copy link
Contributor

jlewi commented Jun 4, 2018

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlewi

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

@lluunn
Copy link
Contributor Author

lluunn commented Jun 4, 2018

/retest

2 similar comments
@lluunn
Copy link
Contributor Author

lluunn commented Jun 4, 2018

/retest

@lluunn
Copy link
Contributor Author

lluunn commented Jun 4, 2018

/retest

@k8s-ci-robot k8s-ci-robot merged commit 0da89b8 into kubeflow:master Jun 4, 2018
wmuizelaar pushed a commit to bolcom/kubeflow that referenced this pull request Jun 5, 2018
* wip

* fix jsonnet

* formatting

* address comments

* fix

* remove namespace from param
@lluunn lluunn deleted the katib1 branch March 21, 2019 21:52
saffaalvi pushed a commit to StatCan/kubeflow that referenced this pull request Feb 11, 2021
* wip

* fix jsonnet

* formatting

* address comments

* fix

* remove namespace from param
yanniszark pushed a commit to arrikto/kubeflow that referenced this pull request Feb 15, 2021
* feat: Support random search

Signed-off-by: Ce Gao <gaoce@caicloud.io>

* feat: Update docs

Signed-off-by: Ce Gao <gaoce@caicloud.io>
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