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

AWS subnet tagging causes hosted clusters to not allow load balancer to be exposed #788

Open
kylewuolle opened this issue Dec 12, 2024 · 0 comments · May be fixed by #810
Open

AWS subnet tagging causes hosted clusters to not allow load balancer to be exposed #788

kylewuolle opened this issue Dec 12, 2024 · 0 comments · May be fixed by #810
Assignees
@kylewuolle
Labels
bug Something isn't working

Comments

@kylewuolle
Copy link
Contributor

Currently the AWS provider will not allow a hosted cluster to create a load balancer that gets assigned an ip or host name. A possible solution is to change the provider template to define the KubernetesClusterTag or KubernetesClusterID variables in the AWS cloud config.
@kylewuolle kylewuolle added the bug Something isn't working label Dec 12, 2024
@kylewuolle kylewuolle self-assigned this Dec 12, 2024
@DinaBelova DinaBelova moved this from Todo to In Progress in Project 2A Dec 17, 2024
@kylewuolle kylewuolle linked a pull request Dec 18, 2024 that will close this issue
Open
@DinaBelova DinaBelova linked a pull request Dec 23, 2024 that will close this issue
Fix AWS hosted cluster template networking issue (fixes #788) #810
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kylewuolle kylewuolle

Labels
bug Something isn't working
Projects
Project 2A
Status: In Progress
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix AWS hosted cluster template networking issue (fixes #788) kylewuolle/hmc
1 participant
@kylewuolle