-
Notifications
You must be signed in to change notification settings - Fork 108
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
Default AWS accounts unusable for KKP? #1462
Comments
My first idea here is that potentially, an internet gateway (or whatever the term is) needs to be attached to the VPC so nodes can go out to the internet. But I'm not sure about that. |
This would be resolved by #1495. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. /close |
@kubermatic-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/reopen |
@embik: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/remove-lifecycle rotten |
We created a fresh AWS account to test KKP. After installing KKP 2.23 into it, we started to create the first usercluster, also on AWS, in the same account.
However the nodes never joined the usercluster. We found out that this is because we had not enabled
Assign Public IP
when creating the MachineDeployment via the KKP dashboard. Once we enabled this, new machines could successfully join the cluster.Our VPC followed the current documentation (i.e.
Enable DNS Hostnames
was enabled).It's unfortunate that KKP's default settings result in a broken cluster.
The text was updated successfully, but these errors were encountered: