-
Notifications
You must be signed in to change notification settings - Fork 32
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
PODAUTO-199: Updates for 4.17 #167
PODAUTO-199: Updates for 4.17 #167
Conversation
@maxcao13: This pull request references PODAUTO-199 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set. 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. |
As discussed on Slack, Nice work on the controller runtime related updates! I think maybe it's time to move off of the Would you mind switching the images in the following files as part of this update?
|
I was looking at it, should |
41bc4d6
to
38cf093
Compare
@maxcao13: This pull request references PODAUTO-199 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set. 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. |
@maxcao13: This pull request references PODAUTO-199 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set. 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. |
Seems like |
38cf093
to
f1f5ebb
Compare
Updated with new release images. |
@maxcao13: This pull request references PODAUTO-199 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set. 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. |
@maxcao13: This pull request references PODAUTO-199 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set. 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. |
Included PODAUTO-202 changes in this PR. EDIT: Although, I'm not sure if the Dockerfile in |
18c7a9e
to
fcb4ea5
Compare
@maxcao13: This pull request references PODAUTO-199 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set. 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. |
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.
I only see one issue with the manifest diff test. Everything else looks great! I'll watch for that to get updated then I'll add the LGTM label.
/approve
Edit: that failing E2E operator test looks like it is actually succeeding. I'm not quite sure why it is tricking CI into thinking it's failing.
fcb4ea5
to
3f44f38
Compare
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: joelsmith, maxcao13 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 |
@maxcao13: 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. |
[ART PR BUILD NOTIFIER] Distgit: vertical-pod-autoscaler-operator |
Updates for 4.17
hack/update-vendor.sh
registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.22-openshift-4.17
in go-fmt, go-vet, Makefile, etc...sed -i 's/4.16/4.17/g' $(git grep -l 4.16 manifests/) images/ci/bundle.Dockerfile hack/manifest-diff-upstream.sh hack/e2e.sh Makefile
FROM registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.22-openshift-4.17
(images/ci/Dockerfile
,images/operator-registry/Dockerfile.registry.ci
,Dockerfile
,Dockerfile.rhel
)openshift/origin-v4.0
toregistry.ci.openshift.org/ocp/4.17:base-rhel9
Had to update some struct initialization and func arguments because of a
controller-runtime
upgrade to v18.4 from v17.0 kubernetes-sigs/controller-runtime#2783