DependencyTrack / DependencyTrack/helm-charts
Include NetworkPolicy in chart
- Dominant language
- Go Template
- Stars
- 78
- Forks
- 55
- Avg merge
- 1h 57m
- Merged PRs (30d)
- 14
Description
It'd be convenient to have NetworkPolicy templates included in the chart for exactly the communication that's needed by the chart, with a `networkPolicy.enabled` value, and some options to configure what pods should be allowed ingress (ingress controller -> api-server/frontend pods).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the chart's templates and values files, then review how existing resources and configurable values are defined. Add an optional NetworkPolicy controlled by networkPolicy.enabled, with ingress configuration for the ingress controller to reach the api-server and frontend pods. Done means the policy renders only when enabled and matches the configured communication needs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100