GKE Autopilot Support for CodeFresh Runner

[SpainTrain]

GKE supports a new cluster type called AutoPilot - https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview. AutoPilot provides very granular billing for pod requests, which is a great conceptual match with CodeFresh Runner hybrid pipelines. However, it appears that CodeFresh runner uses hostPath volume, which is not allowed in AutoPilot (see below).

I understand that this could be a significant change, but having CodeFresh pipeline jobs run on a GKE AutoPilot cluster would be incredibly powerful. This would allow direct resource control for jobs within CodeFresh - updating the pod request values in the pipeline config would in turn increase the request to the cluster, and GKE AutoPilot would automatically run the pod with the requested resources. Such a setup would put resource control directly in the hands of our CI users, and remove a whole exercise of node pool planning (and associated wasted resources).

Error: admission webhook "validation.gatekeeper.sh" denied the request: [denied by autogke-no-write-mode-hostpath] hostPath volume dind-volume-dir in container lv-cleaner is accessed in write mode; disallowed in Autopilot. 

From https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview:

HostPort and hostNetwork are not permitted because node management is handled by GKE. Using hostPath volumes in write mode is prohibited, while using hostPath volumes in read mode is allowed only for /var/log/ path prefixes. Using host namespaces in workloads is prohibited.