linode / linode/cluster-api-provider-linode

Made control-plane NodeBalancer's name dynamic

Open
#363 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
35
Forks
43
Avg merge
23h 12m
Merged PRs (30d)
19

Description

## General:

* [X] Have you removed all sensitive information, including but not limited to access keys and passwords?
* [X] Have you checked to ensure there aren't other open or closed [Pull Requests](https://github.com/linode/cluster-api-provider-linode/pulls) for the same bug/feature/question?

----

## Feature Requests:
* [X] Have you explained your rationale for why this feature is needed?
* [X] 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](https://kubernetes.slack.com/messages/CD4B15LUR/details/) channel `#linode`. To sign up, use the [Kubernetes Slack inviter](http://slack.kubernetes.io/).

The [Linode Community](https://www.linode.com/community/questions/) is a great place to get additional support.

Contributor guide

Open the contributing guide

Research direction

Start in the repository's control-plane NodeBalancer setup and trace how its label is constructed. Change the label so it includes a dynamic suffix, then verify that separate CAPL clusters can create distinct NodeBalancers without conflicts.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.