Create the GCP project

Create a GCP project called pingpong-site1-gcp-demo preferably by using the web console. Make sure you have enabled billing so that you can create resources that costs money.

Making it work smooth with the showcase files

The configuration in the showcase files assumes that your project name for the first part is pingpong-site1-gcp-demo. This is reflected by all files that relate to deployment. You can choose any name of course but you must remember then to update the references to pingpong-site1-gcp-demo in the project files.

Authenticate/connect to the project in console

We're gonna be running a lot of console commands using the SDK so once you have created the project it is a good thing to perform a:

gcloud auth login

This will take you through the familiar Google auth process that you've seen before if you're a Gmail user. Just authenticate as per usual. When completed the console will output a recommendation; - that you set the SDK config to target a specific PROJECT_ID.

If you're not already tied to pingpong-site1-gcp-demo (that we be displayed in the console output if so) then perform:

gcloud config set project pingpong-site1-gcp-demo

If you ever become uncertain about your SDK settings, that can happen(!), then you can always ask:

gcloud config list

That will output something like this:

[core]
account = [email protected]
disable_usage_reporting = True
project = pingpong-site1-gcp-demo
[run]
platform = gke

The project property shows that we are connected to the desired project.

There is no validation performed when you set your PROJECT_ID, so be careful with spelling! Obviously you will find out when trying to perform an action, but it can be a bit tricky to spot the error.

Next, next, next!!!