-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Deprecated apiVersion used for MutatingWebhookConfiguration and CertificateSigningRequest #3873
Comments
Thanks for the heads-up, we'll work on this soon. |
@cPu1 are you actively writing this at the moment? If not can you un-assign and throw it back into the pool? |
In addition to switching to the stable API versions, it will be best to stay away from the Legacy K8s signer, and instead use |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
@cPu1 do you know if we are still blocked upstream on this? |
We're blocked upstream on |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
We have a merged PR that we had to revert temporarily, that will remove the need for installing the VPC controller in order to run Windows workloads, making this issue obsolete. We'll close this issue when we re-merge that PR back. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Not stale, this is blocked on AWS. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
@cPu1 The PR you mentioned is merged, can we close this issue, or is this still blocked upstream? |
This is obsoleted by #4338. |
Hello, when creating a new admission controller, eksctl prints out the following warnings:
This can be reproduced following the instructions here:
https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html#enable-windows-support
VERSIONS
The text was updated successfully, but these errors were encountered: