-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
(aws-eks): Add validate flag to KubernetesManifest class to pass invalidated objects #11763
Comments
Hi, do we have an ETA for this? If not I can switch to EKSCTL for the time being, 😄 |
Closes #11763 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Hello everyone, When will this feature be available? I'm developing a US and I'm facing this exact problem. Thanks in advance! |
This will be available in the next release. |
Thanks @iliapolo ! |
Closes aws#11763 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
It would be great if we could pass unvalidated resources.
Since the flag --validate=false was added to kubectl. We could probably have a constructor attribute called validate.
Use Case
I'm trying to add an ALB ingress controller to the EKS cluster. But right now cannot do that through CDK.
I need to add cert-manager which needs to be run without validation.
Source:EKS-ALB-Ingress-Guide
Proposed Solution
Add constructor props to KubernetesManifest class to include --validate as an boolean argument.
Also add a validate prop to addManifest() function of @aws-cdk/aws-eks.Cluster class
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: