replicatedhq / replicatedhq/kURL
kurl.sh does not support adding node labels
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 809
- Forks
- 81
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 20
Description
There should be a way to set labels on the original node as well as any additional nodes that are added to the cluster. Labels should not be required to be shared between nodes, either.
This can be done manually with kubectl after the fact in many situations, but that also invites race conditions if labels are used for scheduling and the cluster is in active use.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in kurl.sh and trace how the original node and additional cluster nodes are configured. Determine how distinct labels can be supplied per node and verify that labels are applied before scheduling can rely on them; done means both original and additional nodes support independent labels without manual kubectl steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100