kubermatic
Default AWS accounts unusable for KKP?
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.
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.
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale