-
Notifications
You must be signed in to change notification settings - Fork 22
Upgrade operator-sdk to 1.17.0 #59
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
Upgrade operator-sdk to 1.17.0 #59
Conversation
871a0ee
to
824c8ed
Compare
- Update k8s to v1.23.0 - Update controller-runtime to v0.11.0 - Update ginkgo to v1.16.5 - Update gomega to v1.17.0 - Update manifestival to v0.7.1 Per upgrade instructions in https://sdk.operatorframework.io/docs/upgrading-sdk-version/v1.17.0/
- Add target to set up envtest with latest version. Remove script to test with envtest. - Use cancellable context when running tests. This fixes an issue that causes the kube-apiserver process to hang during teardown.
- Update Makefile so it conforms to newer defaults for operator-sdk and controller-runtime. - Upgrade controller-gen to v0.8.0 - Upgrade opm to v1.19.1 - Upgrade operator-sdk to v1.17.0 - Regenerate manifests and bundle
Assign resource requests and limits to the kube-rbac-proxy sidecar, per upgrade instructions. See https://sdk.operatorframework.io/docs/upgrading-sdk-version/v1.17.0/
Add the kubectl default container annotation to the operator deployment, per the upgrade instructions for v1.16.0. See https://sdk.operatorframework.io/docs/upgrading-sdk-version/v1.16.0/#add-annotation-to-specify-the-default-container
824c8ed
to
dfd8d63
Compare
@@ -6,7 +6,7 @@ LABEL operators.operatorframework.io.bundle.manifests.v1=manifests/ | |||
LABEL operators.operatorframework.io.bundle.metadata.v1=metadata/ | |||
LABEL operators.operatorframework.io.bundle.package.v1=shipwright-operator | |||
LABEL operators.operatorframework.io.bundle.channels.v1=alpha | |||
LABEL operators.operatorframework.io.metrics.builder=operator-sdk-v1.13.0+git | |||
LABEL operators.operatorframework.io.metrics.builder=operator-sdk-v1.16.0+git |
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.
The PR title says 1.17.0
, but I only see references to 1.16.0
instead.
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.
Yeah, this seems to be a bug in operator-sdk. The version of the label and the sdk version are always off by 1.
LGTM aside from @otaviof 's question at #59 (comment) if there is an explanation for that @adambkaplan go ahead and post a comment in that thread; otherwise, it does seem like it should be consistent and go to 17 instead of 16 |
Filed operator-framework/operator-sdk#5612 to report the semantic version issue. |
/lgtm |
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.
/approve
Self-approving
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adambkaplan 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 |
Changes
Upgrade to operator-sdk v1.17.0, along with dependencies for controller-runtime and kubernetes:
Fixes #56
/kind cleanup
Submitter Checklist
See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes