aboutsummaryrefslogtreecommitdiffstats
path: root/syz-cluster/kernel-disk/kustomization.yaml
Commit message (Collapse)AuthorAgeFilesLines
* syz-cluster: use kubectl for one-off fetch kernels runAleksandr Nogikh2025-05-211-0/+1
| | | | | Refactor the cron job that pulls the base kernels once in a while to enable its manual triggering without installing the Argo CLI utility.
* syz-cluster: use fileserver for GKEAleksandr Nogikh2025-03-051-1/+0
| | | | | On GKE, it's the ony option for ReadWriteMany PVC. Use a custom storage class definition because we use a non-default VPC.
* syz-cluster: fetch all kernel trees returned by APIAleksandr Nogikh2025-02-181-1/+1
| | | | | | Add another argo workflows cron job that queries Controller for the list of the trees, mounts the shared kernel repository disk and fetches all the queried kernel trees.
* syz-cluster: initial codeAleksandr Nogikh2025-01-221-0/+6
The basic code of a K8S-based cluster that: * Aggregates new LKML patch series. * Determines the kernel trees to apply them to. * Builds the basic and the patched kernel. * Displays the results on a web dashboard. This is a very rudimentary version with a lot of TODOs that provides a skeleton for further work. The project makes use of Argo workflows and Spanner DB. Bootstrap is used for the web interface. Overall structure: * syz-cluster/dashboard: a web dashboard listing patch series and their test results. * syz-cluster/series-tracker: polls Lore archives and submits the new patch series to the DB. * syz-cluster/controller: schedules workflows and provides API for them. * syz-cluster/kernel-disk: a cron job that keeps a kernel checkout up to date. * syz-cluster/workflow/*: workflow steps. For the DB structure see syz-cluster/pkg/db/migrations/*.