Skip to main content
Version: 1.8

GKE Provisioner

Introduction​

This plugin streamlines the creation and configuration of a Google Kubernetes Engine (GKE) cluster on your Google Cloud Platform (GCP). It automates the provisioning process while implementing essential security measures, including a preconfigured firewall that allows access to SSH, HTTP (port 80), 8080, and Kubernetes NodePorts. By automating the GKE provisioning process through this plugin, you can save time, ensure consistency in cluster setup, maintain security standards, and provide a Kubernetes-ready environment for deploying your containerized applications.

caution

The GKE Provisioner plugin creates a Standard GKE Cluster, not an Autopilot GKE cluster.

Prerequisites​

Before integrating the GKE Provisioner plugin make sure that you have a GCP account with valid permissions to provision GKE.


Steps​

  1. Navigate to the Jobs section, click Create, and choose Job.
  2. In the 'Create job' window, enter Job Name and choose a target project.
  3. Click Create Job.
  4. In the 'Configurations' tab, fill the required fields under the 'Source code' section and click Save.
  5. In Workflow Editor, click + Job Pipeline.
  6. Give a name to the workflow and click Create Workflow.
  7. Click Add job pipeline to this workflow.
  8. Fill the required fields in ‘Basic configuration’ tab.
  9. Go to the ‘Tasks to be executed’ tab.
  10. Under ‘Tasks’, click the + Add task button.
  11. Select the GKE Provisioner plugin.
  12. Enter the following user inputs with appropriate values.

User Inputs​

Task Name​

Enter the name of your task

e.g., GKE Provisioner

Description​

Add a brief explanation of the task and the reason for choosing the plugin. Include information for someone else to understand the purpose of the task.

e.g., The GKE Provisioner plugin is integrated for provisioning of GKE cluster.

Input Variables​

VariableFormatDescriptionSample Value
GcpServiceAccountEncodedCredentialSTRINGGCP Service Account credentials (base64 encoded) for GKE cluster creation.ZHVtbXliYXNlNjR2YWx1ZQ==
GkeMinNodesSTRINGMinimum node count for the GKE cluster (default: 1)2
DisplayGkeKubeConfigBOOLFlag to determine if the GKE Kubeconfig should be displayed.true
IdentifierSTRINGBrief description of the GKE cluster's purpose or characteristicsplugin-demo-test
GkeMaxNodesSTRINGMaximum node count for the GKE cluster (default: 3).4
GkeNodeServiceAccountNameSTRINGCustom GCP service account name for node VMs (uses project default if not specified)gke-node-service-account-xyz123
GkeRegionSTRINGGCP region for cluster provisioning (default: us-central1).us-central1
GkeMachineTypeSTRINGMachine type for GKE nodes (default: n1-standard-4).e2-medium
GkeImageTypeSTRINGOS image for GKE nodes (default: COS_CONTAINERD).COS_CONTAINERD
GcpProjectIdSTRINGGCP project ID where the GKE cluster will be created.gcp-68493
GkeClusterVersionSTRINGKubernetes version for the GKE cluster.1.30.2-gke.1587003

Trigger/Skip Condition​

Here you can set conditions to execute or skip the task. You can select Set trigger conditions for the execution of a task or Set skip conditions to skip the task.

Output Variables​

VariableFormatDescription
GkeKubeconfigFilePathSTRINGFile path of the generated GKE cluster kubeconfig

Click Update Pipeline.