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.

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

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

Closed
kylewuolle opened this issue Dec 12, 2024 · 0 comments · Fixed by #810
Closed
Assignees
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
@alex-shl alex-shl added this to k0rdent Jan 3, 2025
@alex-shl alex-shl moved this to In Progress in k0rdent Jan 3, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in k0rdent Jan 10, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in Project 2A Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant