ContainerSolutions / ContainerSolutions/registry-tooling
Change registry port to match nodeport
Open
- Dominant language
- Shell
- Stars
- 70
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
The registry listens on port 5000 by default. If we changed this to match the nodeport, it would allow pods to talk to the registry on the same address.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the registry port and Kubernetes NodePort configuration in the installation entry points; verify how pods address the registry. Done means the registry listens on the NodePort and pods can reach it through the same address.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100