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

Made control-plane NodeBalancer's name dynamic #363

Open
4 tasks done
julsemaan opened this issue Jun 11, 2024 · 0 comments
Open
4 tasks done

Made control-plane NodeBalancer's name dynamic #363

julsemaan opened this issue Jun 11, 2024 · 0 comments

Comments

@julsemaan
Copy link

General:

  • Have you removed all sensitive information, including but not limited to access keys and passwords?
  • Have you checked to ensure there aren't other open or closed Pull Requests for the same bug/feature/question?

Feature Requests:

  • Have you explained your rationale for why this feature is needed?
  • Have you offered a proposed implementation/solution?

Currently, the NodeBalancer setup for the control-plane uses a static non-dynamic name which means it can conflict with existing NodeBalancers or will prevent having multiple CAPL clusters with the same name in the same Linode account. Adding a dynamic suffix to the NB label would provide parity with the rest of the resources created by CAPL


For general help or discussion, join the Kubernetes Slack team channel #linode. To sign up, use the Kubernetes Slack inviter.

The Linode Community is a great place to get additional support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant