Doc request: Describe how to protect the knative broker to be accessed from selected namespaces
Open
kind/eventing
lifecycle/frozen
priority/nice-to-have
- Dominant language
- HTML
- Stars
- 5.1k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
With Istio we could restrict the access to the Knative Broker, using the `AuthorizationPolicy` so that we can allow a number of workloads/namespaces to access different Broker URLs.
Contributor guide
Research direction
No file or test is named. Start by locating the Knative Broker and Istio AuthorizationPolicy documentation, then describe how selected workloads or namespaces can access different Broker URLs. Done means the documentation explains the namespace restrictions and the relevant Broker URL access pattern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100