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

add GCP marketplace application manifest for kubeflow pipelines #1621

Merged
merged 24 commits into from
Aug 27, 2019

Conversation

IronPan
Copy link
Member

@IronPan IronPan commented Jul 15, 2019

By following the GCP Marketplace doc
https://cloud.google.com/marketplace/docs/partners/kubernetes-solutions/

And follow the same structure as other samples
https://github.com/GoogleCloudPlatform/click-to-deploy/tree/master/k8s

Also update the api versions for K8s resources.


This change is Reviewable

@IronPan
Copy link
Member Author

IronPan commented Jul 15, 2019

/assign @eshiroma

@k8s-ci-robot
Copy link
Contributor

@IronPan: GitHub didn't allow me to assign the following users: eshiroma.

Note that only kubeflow members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @eshiroma

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@IronPan
Copy link
Member Author

IronPan commented Jul 16, 2019

/retest

description: |-
Machine Learning Pipeline on Kubernetes
maintainers:
- name: Google Click to Deploy

Choose a reason for hiding this comment

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

Unless the final application will end up in https://github.com/GoogleCloudPlatform/click-to-deploy, can you list Kubeflow-related maintainers info here? (also in the README)

type: string
x-google-marketplace:
type: NAMESPACE

Choose a reason for hiding this comment

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

Include one property for each container image (besides the deployer itself) that you'll use in your app.
https://github.com/GoogleCloudPlatform/marketplace-k8s-app-tools/blob/master/docs/building-deployer-helm.md#parameterize-the-images

The app might still install with mpdev install, but our system relies on properties with x-google-marketplace type: IMAGE for determining which images your app uses (both for publishing them, and then to properly reference those published images at deploy time).

Copy link
Contributor

@neuromage neuromage left a comment

Choose a reason for hiding this comment

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

/lgtm

images:
mysql: mysql:5.6
minio: minio/minio:RELEASE.2018-02-09T22-40-05Z
apiServer: gcr.io/ml-pipeline/api-server:0.1.23
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we templatize the version here and make it the same as the version in application.yaml?

Copy link
Member Author

Choose a reason for hiding this comment

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

thanks. I updated the image tag to use $tag which is required by marketplace.
the $tag doesn't seem to be accessible from application.yaml. For now maybe I'll follow other the marketplace samples.

@k8s-ci-robot k8s-ci-robot removed the lgtm label Jul 31, 2019
@neuromage
Copy link
Contributor

/lgtm

@Ark-kun
Copy link
Contributor

Ark-kun commented Aug 22, 2019

@IronPan This PR seems to be pending for a while.

@k8s-ci-robot k8s-ci-robot removed the lgtm label Aug 23, 2019
@IronPan
Copy link
Member Author

IronPan commented Aug 23, 2019

/assign @huyhg

@k8s-ci-robot
Copy link
Contributor

@IronPan: GitHub didn't allow me to assign the following users: huyhg.

Note that only kubeflow members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @huyhg

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ajchili
Copy link
Member

ajchili commented Aug 27, 2019

/lgtm

@IronPan
Copy link
Member Author

IronPan commented Aug 27, 2019

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: IronPan

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 f63c301 into kubeflow:master Aug 27, 2019
ajchili pushed a commit to ajchili/pipelines that referenced this pull request Aug 28, 2019
…flow#1621)

* move kustomize to subdirectory

* add application cr

* add label application crd can recognize

* Update README.md

* Update README.md

* Update README.md

* add schema

* update

* stage

* add deployer

* sync components

* add components

* fix issues

* add configuration

* fix

* fix

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

6 participants