replicatedhq / replicatedhq/kURL
Ability to customize NodePort Range
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 809
- Forks
- 81
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 20
Description
Overview
Right now we override the default kubeadm NodePort range to 80-60000, but sometimes it would be nice to be able to customize this range in my kURL spec. E.G. something like
spec:
kubernetes:
nodePortRange: 80-62000
Use case
I've got an ActiveMQ that runs on a default port of 61616, and I'd like to keep it on the default port with a NodePort.
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 by locating where the kubeadm NodePort range is overridden and where the kURL Kubernetes spec is parsed and validated. Trace how a proposed nodePortRange value would reach the cluster configuration, then identify the relevant tests or installer checks; done means the range can be set through the shown spec without breaking the default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell, yaml
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100