syz - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	syz-cluster: update README	Aleksandr Nogikh	2025-12-08	1	-1/+41
\| \| \| \|	Include more details about the system.
*	syz-cluster: use unique names for migrate jobs	Aleksandr Nogikh	2025-05-23	1	-0/+1
\| \| \| \| \|	Make k8s generate unique names for migrate jobs to facilitate their run by CI/CD pipelines. Also set job expiration time.
*	syz-cluster: use kubectl for one-off fetch kernels run	Aleksandr Nogikh	2025-05-21	1	-1/+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: split off argo workflows setup	Aleksandr Nogikh	2025-05-21	1	-0/+2
\| \| \| \| \| \| \| \|	We cannot at the same time define Argo CRDs and use them because K8S needs some time to process the CRD creation. To facilitate the installation without errors, split off the step that installs Argo and create a step that waits until CRDs are installed.
*	syz-cluster: update README.md	Aleksandr Nogikh	2025-03-05	1	-1/+1
\| \| \| \| \|	The correct way to initialize the kernel disk is by submitting an argo workflow.
*	syz-cluster: make image prefix and tag configurable	Aleksandr Nogikh	2025-02-26	1	-2/+3
\| \| \| \| \| \| \| \| \|	Accept IMAGE_PREFIX and IMAGE_TAG parameters that allow to reuse the Makefile and a lot of k8s configurations both for local and prod environments. Refactor Makefile: define build-* and push-* rules, use templates to avoid repetition.
*	syz-cluster: update workflow templates with kustomize	Aleksandr Nogikh	2025-02-18	1	-2/+1
\| \| \| \|	This removes one of the required manual steps.
*	syz-cluster: update README.md	Aleksandr Nogikh	2025-02-17	1	-2/+10
\| \| \| \| \|	Use a non-default network plugin for minikube. Reorder the installation steps.
*	syz-cluster: initial code	Aleksandr Nogikh	2025-01-22	1	-0/+37
	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/.