Allow port ranges in dynamic authorization policy resources
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
What problem are you trying to solve?
I am trying to mesh a storage solution called Piraeus which has a component called Linstor Satellite. One of the things the satellites manage are DRBD devices across multiple nodes, which communicate with each other. Within Piraeus, we can define the port range (for example; 7000-7999) that these devices should use for communication. Currently, Linkerd's authorization policy only allows us to specify an individual port.
How should the problem be solved?
The Server resource should accept a single port or a range of ports.
Any alternatives you've considered?
Having a controller running in the cluster that creates each individual authorization policy for each port used.
How would users interact with this feature?
No response
Would you like to work on this feature?
no
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 the Server resource definition and the authorization-policy handling that currently accepts one port. Trace how the resource is validated and translated, then add coverage for a single port and a range such as 7000-7999; done means both forms are accepted and existing policy behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- authorization, networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100