kubernetes / kubernetes/sig-security
Umbrella issue: Migrate CVE feed to run under cloud build
- Dominant language
- Go
- Stars
- 249
- Forks
- 82
- Avg merge
- 7d 12h
- Merged PRs (30d)
- 2
Description
As extensively discussed in the Tooling subproject meetings, we are migrating the CVE feed generation off of the privileged build cluster. The recommended replacement from sig-k8s-infra folks is to run it in Cloud Build.
Overall steps:
- [x] Create a GCP project
- Done in https://github.com/kubernetes/k8s.io/pull/7838
- [ ] Assign permissions for the GCP project
- Documented in kubernetes/sig-security/issues/149
- [ ] Update [GCS bucket permissions](https://github.com/kubernetes/k8s.io/blob/main/infra/gcp/terraform/kubernetes-public/k8s-cve-feed.tf#L29) to allow cloud build job to write to it
- [ ] Define and deploy the cloud build job that will run the generation script
- First step here is to figure out how to do so, probably by reading TF examples in https://github.com/kubernetes/k8s.io/blob/main/infra/gcp/terraform/
Contributor guide
Research direction
Start by reading the linked permissions issue, the GCS bucket resource in infra/gcp/terraform/kubernetes-public/k8s-cve-feed.tf, and the Terraform examples in the k8s.io repository. The work is complete when the required project permissions and bucket access are configured and a deployed Cloud Build job runs the CVE feed generation successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, google-cloud, terraform
- Domain
- cloud, devops, infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100