Replies: 1 comment
-
Hey @misterek, how are you provisioning your clusters? Keep in mind that you must also attach the following policies to your role:
Otherwise this call will fail: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I feel like I'm doing something wrong here. Trying to replicate: https://aws.amazon.com/blogs/containers/reduce-container-startup-time-on-amazon-eks-with-bottlerocket-data-volume/ (manually for now)
I'm stuck on step 1. I'm launching a new node in the same subnet as other BottleRocket nodes are running in (so I'm confident that the networking is fine). I have a Role that has SSM Managed instance Core and ECR Read (same as in the tutorial). Additionally, for testing, ingress and egress are wide open.
No matter what I seem to do, I always get:
` Starting Generate additional settings for Kubernetes...
[ 303.517564] pluto[1354]: Timed out retrieving private DNS name from EC2: deadline has elapsed
[FAILED] Failed to start Generate additional settings for Kubernetes.
`
I've also added standalone-mode = true to the settings. Does there happen to be some other step I'm missing by chance? My settings are just standalone-mode, and enabling the control and admin containers. I have a feeling there's something I'm just missing though.
Beta Was this translation helpful? Give feedback.
All reactions