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-connector label and remove pod name #1542

Merged
merged 5 commits into from
Jul 19, 2019

Conversation

hongye-sun
Copy link
Contributor

@hongye-sun hongye-sun commented Jun 21, 2019

Modify all gcp component yaml to have gcp-connector label.


This change is Reviewable

@Ark-kun
Copy link
Contributor

Ark-kun commented Jun 23, 2019

Is the KFP_POD_NAME env variable unused at this moment?

@gaoning777
Copy link
Contributor

Is the gcp-connector label being used by the backend?

@@ -16,6 +16,9 @@ name: Bigquery - Query
description: |
A Kubeflow Pipeline component to submit a query to Google Cloud Bigquery
service and dump outputs to a Google Cloud Storage blob.
metadata:
labels:
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it possible to use annotation instead of label?

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 have replied in another comment and you probably missed that. Label is better to serve as selector instead of annotation.

https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#equality-based-requirement

@@ -16,6 +16,9 @@ name: Bigquery - Query
description: |
A Kubeflow Pipeline component to submit a query to Google Cloud Bigquery
service and dump outputs to a Google Cloud Storage blob.
metadata:
labels:
add-pod-env: 'true'
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we should have namespace prefix in the key name.

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 feel this label is pretty common and not necessary to be KFP specific. Ideally, we should have a admission control which inject it to all pods in kf cluster.

@Ark-kun
Copy link
Contributor

Ark-kun commented Jul 17, 2019

/lgtm

@hongye-sun
Copy link
Contributor Author

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongye-sun

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 1a0959a into kubeflow:master Jul 19, 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