NVIDIA / NVIDIA/ai-cloud-validation
K8S04-01: Verify the provider participates in the Kubernetes Security Response Committee process
Open
Nobody has claimed this yet.
kubernetes-control-plane
priority-2
- Dominant language
- Python
- Stars
- 27
- Forks
- 33
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 28
Description
Must participate in the Kubernetes Security Response Committee (SRC) process. Must be attempting to join if not part of the security committee. Must be able to:
- Responsibly disclose any discovered vulnerabilities to the Kubernetes SRC
- Receive and respond to embargo notifications from the SRC
- Patch disclosed vulnerabilities in the managed service during embargo prior to public disclosure and in compliance with direction provided from the Kubernetes SRC ensuring that the patching process does not violate embargo or SRC guidance.
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
The issue names no files, tests, or entry points. Start by locating the validation check framework and existing Kubernetes security or provider-participation checks. Done means the provider's SRC participation, vulnerability disclosure, embargo response, and pre-disclosure patching capabilities are verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- security, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100