-
Notifications
You must be signed in to change notification settings - Fork 332
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
OCPBUGS-41365: use appropriate images to avoid overrides in dataplane #4791
OCPBUGS-41365: use appropriate images to avoid overrides in dataplane #4791
Conversation
@Patryk-Stefanski: This pull request references Jira Issue OCPBUGS-41365, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
Skipping CI for Draft Pull Request. |
/approve |
/jira refresh |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Patryk-Stefanski, sjenning 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 |
@sjenning: This pull request references Jira Issue OCPBUGS-41365, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
@Patryk-Stefanski: This pull request references Jira Issue OCPBUGS-41365, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
ea65cfb
to
c6b70aa
Compare
✅ Deploy Preview for hypershift-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/test all |
/retest-required |
/test e2e-kubevirt-aws-ovn-reduced |
/test all |
46aad30
to
73f00d0
Compare
/hold |
d913906
to
29fcacb
Compare
…cause its used in dataplane
29fcacb
to
6153ba0
Compare
/test e2e-aks |
2 similar comments
/test e2e-aks |
/test e2e-aks |
/lgtm |
/hold cancel |
/test e2e-aks |
1 similar comment
/test e2e-aks |
@Patryk-Stefanski: all tests passed! Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
@Patryk-Stefanski: Jira Issue OCPBUGS-41365: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-41365 has been moved to the MODIFIED state. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
[ART PR BUILD NOTIFIER] Distgit: hypershift |
/cherry-pick release-4.17 |
@Patryk-Stefanski: #4791 failed to apply on top of branch "release-4.17":
In response to this:
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-sigs/prow repository. |
What this PR does / why we need it: fixes image registry overrides being used in data plane.
Prereq: openshift/cluster-network-operator#2507
Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)
format, where issue_number might be a GitHub issue, or a Jira story:Fixes # OCPBUGS-41365
Checklist