Skip to content

Latest commit

 

History

History
39 lines (32 loc) · 2.63 KB

GCP_InitialSetup.md

File metadata and controls

39 lines (32 loc) · 2.63 KB
Raw

Kash BDP pipeline for GCP cloud.

We will using the Google Container Registry to store the docker images.
We will using the Google Kubernetes Engine (GKE) for deploying the Application.

We see the steps required to setup the Kash BDP pipeline for Google cloud.

  1. Create a new Service Account for doing the docker push and deployment.
  2. Following IAM policy is required.
IAM Role Purpose
roles/storage.admin Required for docker push and pull
roles/storage.objectViewer Required for deployment
roles/container.developer Required for deployment
  1. Download the service account keys as json file which is newly created users as file.Example the json will look like this.
{
"type": "service_account",
"project_id": "[PROJECT-ID]",
"private_key_id": "[KEY-ID]",
"private_key": "-----BEGIN PRIVATE KEY-----\n[PRIVATE-KEY]\n-----END PRIVATE KEY-----\n",
"client_email": "[SERVICE-ACCOUNT-EMAIL]",
"client_id": "[CLIENT-ID]",
"auth_uri": "https://accounts.google.com/o/oauth2/auth",
"token_uri": "https://accounts.google.com/o/oauth2/token",
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
"client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/[SERVICE-ACCOUNT-EMAIL]"
}
  1. Create jenkins Secret file with the service account keys credentials created above.
    In the ID field, specify a meaningful credential ID value - for example, jenkins-user-for-xyz-artifact-repository. You can use upper- or lower-case letters for the credential ID, as well as any valid separator character. However, for the benefit of all users on your Jenkins instance, it is best to use a single and consistent convention for specifying credential IDs. Note: This field is optional. If you do not specify its value, Jenkins assigns a globally unique ID (GUID) value for the credential ID. Bear in mind that once a credential ID is set, it can no longer be changed.
  2. Make a note of the jenkins secrets, which we will be using going forward.
  3. Install Helms in Google Kubernetes Engine (GKE) cluster.

FAQ