You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to create a new AWS EKS cluster that is compatible with Kubernetes 1.29.
What happened?
A new cluster compatible with Kubernetes 1.27 was created. A little investigation lead to the conclusion that likely redundant white spaces in the empty line between version and vpc were to blame.
It would be great if eksctl tool had either separate validation mode (a la aws cloudformation validate-template ...) or performed YAML validation at each run.
Hello volphy 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website
Hi @volphy, I'm not sure I understand what is the ask here. We have a dry run option that allows you to verify the config before using it: https://eksctl.io/usage/dry-run
What were you trying to accomplish?
I wanted to create a new AWS EKS cluster that is compatible with Kubernetes 1.29.
What happened?
A new cluster compatible with Kubernetes 1.27 was created. A little investigation lead to the conclusion that likely redundant white spaces in the empty line between
version
andvpc
were to blame.It would be great if eksctl tool had either separate validation mode (a la
aws cloudformation validate-template ...
) or performed YAML validation at each run.How to reproduce it?
Real identifiers redacted to pseudo-values.
Anything else we need to know?
My environment:
Versions
The text was updated successfully, but these errors were encountered: