-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Support v1 admission webhooks #3167
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
Conversation
Signed-off-by: Maartje Eyskens <maartje@eyskens.me>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: meyskens 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 |
metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" | ||
"k8s.io/apimachinery/pkg/runtime" | ||
"k8s.io/apimachinery/pkg/types" | ||
"k8s.io/klog/klogr" | ||
|
||
"github.com/jetstack/cert-manager/pkg/internal/api/validation" | ||
"github.com/jetstack/cert-manager/pkg/webhook/handlers/testdata/apis/testgroup/install" | ||
"github.com/jetstack/cert-manager/pkg/webhook/handlers/testdata/apis/testgroup/v1" | ||
"github.com/jetstack/cert-manager/pkg/webhook/handlers/testdata/apis/testgroup/v2" | ||
v1 "github.com/jetstack/cert-manager/pkg/webhook/handlers/testdata/apis/testgroup/v1" |
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.
Not entirely sure why goimports
did this...
/test pull-cert-manager-e2e-v1-15 |
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.
Looks good, except for a query about the helm hack.
Signed-off-by: Maartje Eyskens <maartje@eyskens.me>
/lgtm |
What this PR does / why we need it:
This adds support for admissionregistration.k8s.io/v1. Both in deployment and webhook server.
It will be the default version in the normal manifests, the legacy version will use v1beta1.
All code paths are changed to be v1, if v1beta1 is sent it will convert it to v1 and back to v1beta1 in response, this is done to keep supporting the legacy versions while being ready for v1beta1 being removed in future releases of Kubernetes
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #fixes #2952
Release note:
/kind cleanup