Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Default AWS accounts unusable for KKP? #1462

Open
xrstf opened this issue Jun 13, 2023 · 8 comments
Open

Default AWS accounts unusable for KKP? #1462

xrstf opened this issue Jun 13, 2023 · 8 comments

Comments

@xrstf
Copy link
Contributor

xrstf commented Jun 13, 2023

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.
@embik
Copy link
Member

embik commented Jun 13, 2023

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.

@embik
Copy link
Member

embik commented Jul 17, 2023

This would be resolved by #1495.

@kubermatic-bot
Copy link
Contributor

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

@kubermatic-bot kubermatic-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 15, 2023
@embik
Copy link
Member

embik commented Nov 8, 2023

/remove-lifecycle stale

@kubermatic-bot kubermatic-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 8, 2023
@kubermatic-bot
Copy link
Contributor

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

@kubermatic-bot kubermatic-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 6, 2024
@embik
Copy link
Member

embik commented Feb 6, 2024

/remove-lifecycle stale

@kubermatic-bot kubermatic-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 6, 2024
@kubermatic-bot
Copy link
Contributor

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

@kubermatic-bot kubermatic-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 6, 2024
@embik
Copy link
Member

embik commented May 6, 2024

/remove-lifecycle stale

@kubermatic-bot kubermatic-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xrstf @embik @kubermatic-bot