-
Notifications
You must be signed in to change notification settings - Fork 15
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
NE-1808: Bump k8s.io, openshift, controller-runtime modules and golang #143
NE-1808: Bump k8s.io, openshift, controller-runtime modules and golang #143
Conversation
@alebedev87: This pull request references NE-1808 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.19.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. |
/test e2e-aws-proxy-operator AWS jobs run slow recently (a rush before Christmas?). |
/retest Step e2e-aws-proxy-operator-optional-operators-subscribe failed after 33m0s |
@@ -1,4 +1,4 @@ | |||
build_root_image: | |||
name: release | |||
namespace: openshift | |||
tag: rhel-8-release-golang-1.19-openshift-4.12 | |||
tag: rhel-8-release-golang-1.22-openshift-4.17 |
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.
can we change to rhel-9-release
?`
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.
RHEL9 migration is something we need to do, not only in this repository. Unfortunately I don't think I'll have enough time to do it for this release (before Christmas break). So, we need to file a bug for RHEL9 migration similar to what we did for the externaldns.
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.
OK. then other look good.
@ShudiLi could you please help file a bug.
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.
@lihongan Filed https://issues.redhat.com/browse/OCPBUGS-46442, thanks.
08fb760
to
1c295fa
Compare
Bumped |
/retest |
@alebedev87: This pull request references NE-1808 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.19.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. |
@alebedev87: This pull request references NE-1808 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.19.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. |
1c295fa
to
5b6be45
Compare
@alebedev87: This pull request references NE-1808 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.19.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. |
Migrated infrastructure CRD retrieval to the new package |
5b6be45
to
f088591
Compare
/retest |
tested it with 4.18.0-0.ci.test-2024-12-17-024008-ci-ln-gi4bdmb-latest
|
/label qe-approved |
@alebedev87: This pull request references NE-1808 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.19.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. |
/retest |
f088591
to
ab822ce
Compare
- Bumped golang to 1.22: - Update go.mod - Update Dockerfiles - Bumped k8s.io/* modules to 0.30.3 and OpenShift API to 20240812094746-86145edb40cf. - Bumped controller-runtime to 0.18.5: - Manager's `Port` option removed, now using dedicated webhook server field (kubernetes-sigs/controller-runtime#2422). - Manager's `MetricsBindAddress` option removed, now using dedicated metrics server field (kubernetes-sigs/controller-runtime#2407). - Cache's `Namespaces` option replaced by `DefaultNamespaces` (kubernetes-sigs/controller-runtime#2421). - Bumped aws-load-balancer-controller to f39ae43121c3 to use latest CRD scheme in e2e tests. - Regenerated CRD and bundle manifests using `make bundle` command. - Bumped `kustomize` to v5 to fix a conflict caused by k8s.io bumps: - `kyaml` unable to use the bumped `github.com/google/gnostic-models/openapiv2` package. - Removed `TypeMeta` from expected deployment object when it's compared to structured one retrieved from fake client (kubernetes-sigs/controller-runtime#2633). - Migrated infrastructure CRD retrieval to the new package `zz_generated.crd-manifests`: - Updated infrastructure CRD for unit tests using `make update-vendored-crds` command. - Updated envtest setup to use the downstream index. - Infrastructure CRD uses CEL functions backported from newer k8s API. - Upstream `envtest` is not ready to use newer CEL function. - Bumped `setup-envtest` to be able to use `--index` flag.
ab822ce
to
56f3ebb
Compare
To fix the unit test:
|
@alebedev87: This pull request references NE-1808 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.19.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. |
@alebedev87: This pull request references NE-1808 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.19.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. |
/label px-approved The docs are enough for this feature. |
/label docs-approved |
Conflict on the WAF ACL resource: fix PR. /test e2e-aws-operator |
/test e2e-aws-proxy-operator |
/label qe-approved |
/test e2e-aws-operator |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alebedev87 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 |
@alebedev87: 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. |
Bumped aws-load-balancer-controller to f39ae43121c3 to use latest CRD scheme in e2e tests.- Bumped golang to 1.22:
- Update go.mod
- Update Dockerfiles
Bumped k8s.io/* modules to 0.30.3 and OpenShift API to 20240812094746-86145edb40cf.
Bumped controller-runtime to 0.18.5:
Port
option removed, now using dedicated webhook server field (⚠ Remove deprecated manager, webhook and cluster options kubernetes-sigs/controller-runtime#2422).MetricsBindAddress
option removed, now using dedicated metrics server field (⚠ Introduce Metrics Options struct & secure metrics serving kubernetes-sigs/controller-runtime#2407).Namespaces
option replaced byDefaultNamespaces
(⚠️ Allow configuring more granular cache filtering kubernetes-sigs/controller-runtime#2421).Bumped aws-load-balancer-controller to
f39ae43121c3
to use latest CRD scheme in e2e tests.Regenerated CRD and bundle manifests using
make bundle
command.Bumped
kustomize
to v5 to fix a conflict caused by k8s.io bumps:kyaml
unable to use the bumpedgithub.jparrowsec.cn/google/gnostic-models/openapiv2
package.Removed
TypeMeta
from expected deployment object when it's compared to structured one retrieved from fake client (⚠️ Fakeclient: Only set TypeMeta for unstructured kubernetes-sigs/controller-runtime#2633).Migrated infrastructure CRD retrieval to the new package
zz_generated.crd-manifests
:make update-vendored-crds
command.Updated envtest setup to use the downstream index.
Commands to reproduce the bump: