Cluster Peering exported service wildcard
Open
theme/cluster-peering
theme/operator-usability
type/question
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
#### Feature Description
When exporting a service for peering, we should support wildcards. If cluster wants to export multiple services, it can be a pain to export each service. If a group is changing services constantly then maintaining the peering configs become a burden.
Contributor guide
Research direction
The issue does not name files, tests, or entry points. Start by locating the cluster peering service-export configuration and its current service matching logic; then determine how wildcard patterns should select multiple services. Done means peering exports can use a wildcard without listing each service individually and existing explicit exports continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100