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

MetadataStore: Update to release metadata-envoy in each release #4026

Conversation

dushyanthsc
Copy link
Contributor

Metadata envoy image was built in every build but only release for marketplace. This change releases metadata-envoy image for OSS also in each release.

@k8s-ci-robot k8s-ci-robot requested review from Bobgy and IronPan June 18, 2020 23:53
@kubeflow-bot
Copy link

This change is Reviewable

@dushyanthsc
Copy link
Contributor Author

/assign @rmgogogo
/assing @Bobgy

@dushyanthsc
Copy link
Contributor Author

@rmgogogo , @Bobgy I think I have missed one place where there is the image tag substitution but can't figure out where, can you kindly point that out.

@rmgogogo
Copy link
Contributor

/lgtm
/approve

not sure whether it will be updated in another PR
https://github.com/kubeflow/pipelines/blob/master/manifests/kustomize/base/kustomization.yaml#L31

and test
https://github.com/kubeflow/pipelines/blob/master/test/deploy-pipeline-lite.sh#L63

/hold
hold to address the upper comment. If in another PR, feel free to submit this one first.

@Bobgy
Copy link
Contributor

Bobgy commented Jun 19, 2020

In addition to what @rmgogogo provided, you also need to build the image for each presubmit test in https://github.com/kubeflow/pipelines/blob/master/test/cloudbuild/batch_build.yaml#L40

You need these changes in the same PR to pass e2e tests

@dushyanthsc dushyanthsc force-pushed the dushyanthsc/metadata-envoy-integration branch from 59ff06c to de90c24 Compare June 22, 2020 21:37
@k8s-ci-robot k8s-ci-robot removed the lgtm label Jun 22, 2020
@dushyanthsc
Copy link
Contributor Author

I updated the pointed files. Looks like its still is not sufficient.

waitFor: ['pullMetadataEnvoy']
- id: 'tagMetadataEnvoyCommitSHA'
name: 'gcr.io/cloud-builders/docker'
args: ['tag', 'gcr.io/$PROJECT_ID/metadata-writer:$COMMIT_SHA', 'gcr.io/ml-pipeline/metadataenvoy:$COMMIT_SHA']
Copy link
Contributor

Choose a reason for hiding this comment

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

a typo?
metadata-writer -> metadataenvoy

@dushyanthsc dushyanthsc force-pushed the dushyanthsc/metadata-envoy-integration branch from de90c24 to 0e8cbe1 Compare June 23, 2020 04:01
Copy link
Contributor

@Bobgy Bobgy left a comment

Choose a reason for hiding this comment

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

Thanks @dushyanthsc!
There's one minor issue

@@ -398,8 +406,8 @@ steps:
- |
docker tag gcr.io/$PROJECT_ID/metadata-envoy:$COMMIT_SHA gcr.io/ml-pipeline/google/pipelines/metadataenvoy:$(cat /workspace/mm.ver)
docker tag gcr.io/$PROJECT_ID/metadata-envoy:$COMMIT_SHA gcr.io/ml-pipeline/google/pipelines-test/metadataenvoy:$(cat /workspace/mm.ver)
docker push gcr.io/ml-pipeline/google/pipelines/metadataenvoy:$(cat /workspace/mm.ver)
docker push gcr.io/ml-pipeline/google/pipelines-test/metadataenvoy:$(cat /workspace/mm.ver)
docker push gcr.io/ml-pipeline/google/pipelines/metadata-envoy:$(cat /workspace/mm.ver)
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 might have not been clear enough.
For standalone deployment images, we should use - separated.
For marketplace images, there cannot be -s in them.

These are below /google/ directory, so they are marketplace images

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sorry I think it my mistake, I didn't read the path correctly. I have fixed it now.

@dushyanthsc dushyanthsc force-pushed the dushyanthsc/metadata-envoy-integration branch from 0e8cbe1 to 1e07313 Compare June 23, 2020 06:57
@Bobgy
Copy link
Contributor

Bobgy commented Jun 23, 2020

Thanks @dushyanthsc!
I think this is right now.
/lgtm
/approve

note the entire test infra is failing, we might want to retry these tests tomorrow to see if they recover

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bobgy, rmgogogo

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

@Bobgy
Copy link
Contributor

Bobgy commented Jun 23, 2020

/unhold

@Bobgy Bobgy added do-not-merge/hold cherrypick-approved area OWNER approves to cherry pick this PR to current active release branch labels Jun 23, 2020
@dushyanthsc
Copy link
Contributor Author

/retest

@Ark-kun
Copy link
Contributor

Ark-kun commented Jun 23, 2020

/retest

@dushyanthsc
Copy link
Contributor Author

@Bobgy Can you remove the "do-not-merge/hold label" if the changes are good. Thanks

@Bobgy
Copy link
Contributor

Bobgy commented Jun 24, 2020

Sorry, that was a mistake.... github UI has concurrent conflicts when doing two actions at the same time.
/unhold

@k8s-ci-robot k8s-ci-robot merged commit bc3c59a into kubeflow:master Jun 24, 2020
@Bobgy Bobgy added the cherrypicked cherry picked to release branch `release-x.y` label Jul 2, 2020
Jeffwan pushed a commit to Jeffwan/pipelines that referenced this pull request Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved cherrypick-approved area OWNER approves to cherry pick this PR to current active release branch cherrypicked cherry picked to release branch `release-x.y` lgtm size/S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants