Ilya Dmitrichenko

Right now user can specify zone and region, or rely on defaults. They should instead be able to just specify which region they want, and whether a regional (#17) or...

The primary need for this is to remove hardcoded defaults for: ```Go c.Spec.Project = "cilium-ci" c.Spec.Location = "europe-west2-b" c.Spec.Region = "europe-west2" c.Spec.JobSpec.Runner.Image = "quay.io/isovalent/gke-test-cluster-gcloud:803ff83d3786eb38ef05c95768060b0c7ae0fc4d" c.Spec.JobSpec.Runner.InitImage = "quay.io/isovalent/gke-test-cluster-initutil:854733411778d633350adfa1ae66bf11ba658a3f" ``` There should...

The operator currently assumes single-zone use-case for its cost advantage, however it should be possible for the user to request a regional cluster.

This will make log extraction easier and generally simplify what it takes to find the job that belongs to a particular run, especially using GitHub metadata. Adding some of the...

Events can be quite helpful in troubleshooting lifecycle of a resource, it'd be good to send events on major status updates (e.g. #14), and on any key dependency events, especially...

This is need in oder to indicate clearly whether tests started or not. This should probably be part of `status.condtions` and not `status.dependencies`, since `status.dependencies` is used to determine whether...

When the Config Connector sees all new objects, it builds a dependency graph to create underlying GCP object in the right order. Namely, when it sees `ContainerCluster`, `ContainerNodePool`, `ComputeNetwork` and...

Issues like https://github.com/isovalent/gke-test-cluster-operator/issues/11 currently don't get caught in any way and are not visible from a PR status. Perhaps requester could catch some of these, as it maybe generally useful...