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

PODAUTO-199: Updates for 4.17 #167

Merged
merged 2 commits into from
Jul 23, 2024

Conversation

maxcao13
Copy link
Contributor

@maxcao13 maxcao13 commented Jul 4, 2024

Updates for 4.17

  • Update deps
    • edit (update to 4.17/0.30.2) and run hack/update-vendor.sh
  • Update code and build to match updated deps
  • Update go version to go 1.22 (go.mod, Dockerfile, images/ci/Dockerfile, Makefile)
  • Switched from old images to updated ci tooling images registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.22-openshift-4.17 in go-fmt, go-vet, Makefile, etc...
  • Rev version from 4.16 -> 4.17: 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
  • Verify that Dockerfile.rhel7 & .ci-operator.yaml are up to date (they are. Thanks, ART team!)
  • Update manifests to match upstream
  • Updated ci + release images to 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)
  • Updated ci base image from openshift/origin-v4.0 to registry.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

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 4, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 4, 2024

@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:

Updates for 4.16

  • Update deps
  • edit (update to 4.17/0.30.2) and run hack/update-vendor.sh
  • Update code and build to match updated deps
  • Update go version to go 1.22 (go.mod, Dockerfile, images/ci/Dockerfile, Makefile) (cannot update vet/lint/upstream-manifest because openshift/release doesnt seem to have 1.22 tag yet)
  • Rev version from 4.16 -> 4.17: sed -i 's/4.16/4.17/g' $(git grep -l 4.15 manifests/) images/ci/bundle.Dockerfile hack/manifest-diff-upstream.sh hack/e2e.sh Makefile
  • Verify that Dockerfile.rhel7 & .ci-operator.yaml are up to date (they are. Thanks, ART team!)
  • Update manifests to match upstream

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

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.

@openshift-ci openshift-ci bot requested review from joelsmith and wangchen615 July 4, 2024 22:09
@joelsmith
Copy link
Contributor

joelsmith commented Jul 8, 2024

As discussed on Slack, sed -i 's/4.16/4.17/g' $(git grep -l 4.15 manifests/) should have been sed -i 's/4.16/4.17/g' $(git grep -l 4.16 manifests/)

Nice work on the controller runtime related updates!

I think maybe it's time to move off of the openshift/origin-release:golang-1.XX and registry.ci.openshift.org/openshift/release:golang-1.XX images and use the registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.XX-openshift-4.YY images since those seem to be updated regularly while the others don't.

Would you mind switching the images in the following files as part of this update?

Makefile
hack/go-fmt.sh
hack/go-lint.sh
hack/go-vet.sh
hack/manifest-diff-upstream.sh
hack/manifest-diff.sh

@maxcao13
Copy link
Contributor Author

maxcao13 commented Jul 9, 2024

I was looking at it, should golint and its scripts + ci yamls still exist? It seems to be deprecated in favour of go vet and Staticcheck https://github.com/golang/lint

@maxcao13 maxcao13 force-pushed the 4.17-release-chores branch from 41bc4d6 to 38cf093 Compare July 10, 2024 00:07
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 10, 2024

@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:

Updates for 4.17

  • Update deps
  • edit (update to 4.17/0.30.2) and run hack/update-vendor.sh
  • Update code and build to match updated deps
  • Update go version to go 1.22 (go.mod, Dockerfile, images/ci/Dockerfile, Makefile) (cannot update vet/lint/upstream-manifest because openshift/release doesnt seem to have 1.22 tag yet)
  • Rev version from 4.16 -> 4.17: 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
  • Verify that Dockerfile.rhel7 & .ci-operator.yaml are up to date (they are. Thanks, ART team!)
  • Update manifests to match upstream

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

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.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 10, 2024

@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:

Updates for 4.17

  • Update deps
  • edit (update to 4.17/0.30.2) and run hack/update-vendor.sh
  • Update code and build to match updated deps
  • Update go version to go 1.22 (go.mod, Dockerfile, images/ci/Dockerfile, Makefile)
  • Switched from old images to updated registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.22-openshift-4.17 in go-fmt, go-vet, Makefile, etc...
  • Rev version from 4.16 -> 4.17: 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
  • Verify that Dockerfile.rhel7 & .ci-operator.yaml are up to date (they are. Thanks, ART team!)
  • Update manifests to match upstream

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

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
Copy link
Contributor Author

Seems like registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.22-openshift-4.17 doesn't include jq and that causes manifest-diff*.sh scripts to fail.

@maxcao13 maxcao13 force-pushed the 4.17-release-chores branch from 38cf093 to f1f5ebb Compare July 11, 2024 15:41
@maxcao13
Copy link
Contributor Author

Updated with new release images.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 11, 2024

@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:

Updates for 4.17

  • Update deps
  • edit (update to 4.17/0.30.2) and run hack/update-vendor.sh
  • Update code and build to match updated deps
  • Update go version to go 1.22 (go.mod, Dockerfile, images/ci/Dockerfile, Makefile)
  • Switched from old images to updated ci tooling images registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.22-openshift-4.17 in go-fmt, go-vet, Makefile, etc...
  • Rev version from 4.16 -> 4.17: 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
  • Verify that Dockerfile.rhel7 & .ci-operator.yaml are up to date (they are. Thanks, ART team!)
  • Update manifests to match upstream

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

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.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 22, 2024

@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:

Updates for 4.17

  • Update deps
  • edit (update to 4.17/0.30.2) and run hack/update-vendor.sh
  • Update code and build to match updated deps
  • Update go version to go 1.22 (go.mod, Dockerfile, images/ci/Dockerfile, Makefile)
  • Switched from old images to updated ci tooling images registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.22-openshift-4.17 in go-fmt, go-vet, Makefile, etc...
  • Rev version from 4.16 -> 4.17: 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
  • Verify that Dockerfile.rhel7 & .ci-operator.yaml are up to date (they are. Thanks, ART team!)
  • Update manifests to match upstream
  • Updated ci + release images to FROM registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.22-openshift-4.17
  • Updated ci base image from openshift/origin-v4.0 to registry.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

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
Copy link
Contributor Author

maxcao13 commented Jul 22, 2024

Included PODAUTO-202 changes in this PR.

EDIT: Although, I'm not sure if the Dockerfile in images/ci/Dockerfile is actually being used anywhere. Here's the current config in openshift/release: https://github.com/openshift/release/blob/17ca3ef1f06212c127e5ea483b9a4d825370aeeb/ci-operator/config/openshift/vertical-pod-autoscaler-operator/openshift-vertical-pod-autoscaler-operator-master.yaml
Does anyone happen to know?

@maxcao13 maxcao13 force-pushed the 4.17-release-chores branch from 18c7a9e to fcb4ea5 Compare July 22, 2024 22:42
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 22, 2024

@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:

Updates for 4.17

  • Update deps
  • edit (update to 4.17/0.30.2) and run hack/update-vendor.sh
  • Update code and build to match updated deps
  • Update go version to go 1.22 (go.mod, Dockerfile, images/ci/Dockerfile, Makefile)
  • Switched from old images to updated ci tooling images registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.22-openshift-4.17 in go-fmt, go-vet, Makefile, etc...
  • Rev version from 4.16 -> 4.17: 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
  • Verify that Dockerfile.rhel7 & .ci-operator.yaml are up to date (they are. Thanks, ART team!)
  • Update manifests to match upstream
  • Updated ci + release images to 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)
  • Updated ci base image from openshift/origin-v4.0 to registry.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

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.

Copy link
Contributor

@joelsmith joelsmith left a 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.

hack/manifest-diff.sh Outdated Show resolved Hide resolved
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 23, 2024
@maxcao13 maxcao13 force-pushed the 4.17-release-chores branch from fcb4ea5 to 3f44f38 Compare July 23, 2024 15:27
Copy link
Contributor

@joelsmith joelsmith left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 23, 2024
Copy link
Contributor

openshift-ci bot commented Jul 23, 2024

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Contributor

openshift-ci bot commented Jul 23, 2024

@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.

@openshift-merge-bot openshift-merge-bot bot merged commit d0b168e into openshift:master Jul 23, 2024
10 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: vertical-pod-autoscaler-operator
This PR has been included in build ose-vertical-pod-autoscaler-operator-container-v4.18.0-202407232010.p0.gd0b168e.assembly.stream.el9.
All builds following this will include this PR.

@maxcao13 maxcao13 deleted the 4.17-release-chores branch August 6, 2024 23:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants