GKE Run Job with YAML

YAML parameters for GKE Run Job

NameTypeDescription
action RequiredStringThe ID of the action.
type RequiredStringThe type of the action. Should be set to KUBERNETES_RUN_JOB.
integration RequiredIntegrationThe ID of the Google integration.
gke_auth_type RequiredStringAuthorization type. Set to SERVICE_ACCOUNT.
zone_id RequiredStringThe ID of the GKE zone.
cluster RequiredStringThe ID of the GKE cluster.
application_id RequiredStringThe ID of the GKE application.
record_argStringRecord current kubectl command in the resource annotation. Can be one of TRUE, FALSE or NOT_SET. If set to false, do not record the command. If set to true, record the command. If not set, default to updating the existing annotation value only if one already exists.
config_pathStringThe repository path to the configuration file. One of config_path or content must be specified.
leave_afterBooleanDefines whether to leave the Pod or delete it after the action finishes.
contentStringThe configuration content. One of config_path or content must be specified.
not_waitBooleanDefines whether the execution should or should not wait for job to end.
kubectl_versionStringVersion of the kubectl used in the action. Default is <latest<.

YAML example for GKE Run Job

yaml
actions: - action: "Run job" type: "KUBERNETES_RUN_JOB" trigger_time: "ON_EVERY_EXECUTION" zone_id: "europe-west1-c" cluster: "cluster-1" application_id: "tokyo-house-138923" gke_auth_type: "SERVICE_ACCOUNT" config_path: "config.yaml" leave_after: true not_wait: true integration: "my_integration"

Last modified on Sep 24, 2024