-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Enable 'status' subresource on CRDs #1922
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: munnerz 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 |
.. note:: | ||
From cert-manager v0.10.0 onwards, the minimum supported version of | ||
Kubernetes is v1.10.0. Users still running Kubernetes 1.9 or below should | ||
upgrade to a supported version before installing cert-manager. |
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'm glad this text is here. It possibly missing was the only part of this PR that had me worried. :)
/retest |
2b99a0a
to
ce07f9a
Compare
/retest |
1 similar comment
/retest |
ce07f9a
to
df7c132
Compare
Signed-off-by: James Munnelly <james@munnelly.eu>
df7c132
to
ed7522e
Compare
Signed-off-by: James Munnelly <james@munnelly.eu>
Signed-off-by: James Munnelly <james@munnelly.eu>
ed7522e
to
3977289
Compare
/retest |
1 similar comment
/retest |
/test pull-cert-manager-e2e-v1-15 |
@munnerz: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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/test-infra repository. I understand the commands that are listed here. |
Closing in favour of #2097 |
What this PR does / why we need it:
This patches enables the 'status' subresource on our CRDs and switches the controllers over to use
UpdateStatus
instead ofUpdate
.This has been supported in Kubernetes since v1.8 or v1.9, and enabled by default (i.e. on GKE etc) since 1.10.
Given that Kubernetes 1.11 is now the oldest supported version (as of 1.15 being recently released), we are now 6mths clear of EOL for k8s 1.9. I think it's now probably safe to switch this and break compatibility with Kubernetes 1.9 (making our minimum supported version 1.10).
Release note: