-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Fix inverse proxy agent in e2e tests #2566
Fix inverse proxy agent in e2e tests #2566
Conversation
- "$_GCR_BASE/viewer-crd-controller" | ||
- "$_GCR_BASE/visualization-server" | ||
- "$_GCR_BASE/inverse-proxy-agent" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
images put here will be pushed to gcr, inverse proxy agent was built but forgot to be pushed
/lgtm |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Bobgy 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 |
This doesn't fully fix the issue. inverse-proxy-agent is now in |
Follow up fix: #2568 |
Even in a successful test, we can see inverse proxy is in ImagePullBackOff state. It's not used in any e2e tests, so it doesn't break presubmit.
example log: https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/kubeflow_pipelines/2563/kubeflow-pipeline-e2e-test/1192300433008234496#1:build-log.txt%3A1426
However, this issue breaks image caching. Inverse proxy agent is always not in gcr because we didn't push it there. This PR fixes the issue.
Benefit of the fix: rerunning tests will skip the image building step.
/assign @jingzhang36
This change is