-
Notifications
You must be signed in to change notification settings - Fork 321
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
[EKS] [BUG] EKS breaks when cluster's launched with a HEX name #2513
Comments
Looks legit. The regex pattern mentioned in the docs does validate it.
|
@teocns have you already reached out to AWS EKS support? |
Yep we confirmed this bug with support case # 173559286800063. I've been indicated to open an issue here |
@teocns you mean something like |
Bare hex names. I probably deployed around 50 clusters, all with incremental hex names while figuring why it didn't work: |
@teocns |
My guts tell me somewhere down the pipeline it is not being escaped and therefore crashes some process or produces unexpected side effects. If that's true, this leaves room for attack vectors |
When deploying EKS clusters with hex names (i.e
0x01
), the cluster silently breaks and never comes alive. Any attempt in accessing the cluster results in a failure as managed cluster access (aws-auth
) does not get configured.Only meaningful logs I managed to collect during experiments:
Relevant slack thread
The text was updated successfully, but these errors were encountered: