Skip to content

Made control-plane NodeBalancer's name dynamic #363

Description

@julsemaan

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions