Mapped port-forwards don't seem to work
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
k8s_resource('blah', port_forwards=[80]) # works 🥳
k8s_resource('blah', port_forwards=['80']) # works 🎉
k8s_resource('blah', port_forwards=80) # works 🌈
k8s_resource('blah', port_forwards='80') # works ✨
k8s_resource('blah', port_forwards=['80:80']) # doesn't work 😢
k8s_resource('blah', port_forwards='80:80') # doesn't work 😢
deployed k8s service:
...snip...
spec:
type: LoadBalancer
ports:
- name: http
protocol: TCP
port: 80
targetPort: 8080
nodePort: 32123
- name: https
protocol: TCP
port: 443
targetPort: 8443
nodePort: 30050
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 tracing how k8s_resource handles the port_forwards argument, using the working scalar examples and the failing mapped forms as a reproduction case. Test against the shown Kubernetes Service, and consider the issue done when both mapped forms work for the service's port and targetPort configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100