Skip to content

Conversation

@a-nogikh
Copy link
Collaborator

@a-nogikh a-nogikh commented Mar 3, 2025

Add the GKE config overlay and address the bugs/incompatibilities that popped up when deploying on GKE.
See individual commits.

The correct way to initialize the kernel disk is by submitting an argo
workflow.
They must relate to argo-executor-ksa and argo-controller-ksa.

Use ClusterRole since the entities are in different namespaces.
Only replace the variables we intended to fix.
This should fix the kernel-disk cron.
The overlays generate the configs for the deployment in the GKE
environment.
Make sure the patches are correctly stacked up.
For now, use strategic patch merge.
This will let us use more granular IAM permissions.
On GKE, it's the ony option for ReadWriteMany PVC.
Use a custom storage class definition because we use a non-default VPC.
@a-nogikh a-nogikh requested a review from tarasmadan March 3, 2025 11:52
@a-nogikh a-nogikh changed the title syz-cluster: move to GKE syz-cluster: add GKE as a supported deployment environment Mar 3, 2025
tarasmadan
tarasmadan previously approved these changes Mar 5, 2025
@a-nogikh a-nogikh force-pushed the features/syz-cluster-gke-configs branch from 8d6c4db to b41f692 Compare March 5, 2025 11:32
@a-nogikh a-nogikh added this pull request to the merge queue Mar 5, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 5, 2025
@a-nogikh a-nogikh added this pull request to the merge queue Mar 5, 2025
Merged via the queue into google:master with commit 3ec8cfc Mar 5, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants