nofusscomputing / nofusscomputing/kubernetes
Setup Manifest SAST
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 0
- Forks
- 0
- Avg merge
- 2h 36m
- Merged PRs (30d)
- 24
Description
To assist with the security of the manifests they should be scanned for potential problems.
Details
Setup a SAST scanner for the manifests. The manifests must be fully tested in their expanded state, including any components and overlays.
Links
Requirements
- Base is scanned
- Each Overlay with the base is scanned
- Each component with the base is scanned
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 reviewing the repository's Kubernetes manifests and the Kubescape and Trivy documentation linked in the issue, then determine how the base, overlays, and components are expanded for scanning. Done means a scanner is configured and the base, every overlay with the base, and every component with the base are all scanned successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100