app-engine-python
gcloud components install app-engine-pythonkubectl
gcloud components install kubectl
Authenticating with Google Cloud services requires a JSON file which we call the account file.
This file is downloaded directly from the Google developers Console. To make the process more straightforwarded, it is documented here:
- Log into the Google developer's Console and select a project.
- The API Manager view should be selected, click on "Credentials" on the left, then "Create credentials", and finally "Service account key".
- Select "Compute Engine default service account" in the "Service account" dropdown, and select "JSON" as the key type.
- Clicking "Create" will download your credentials.
# terraform init
Initializing provider plugins...
- Checking for available provider plugins on https://releases.hashicorp.com...
- Downloading plugin for provider "google" (1.4.0)...
....... truncated
do so if necessary.
terraform plan -out demo-k8s-gke.state
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
------------------------------------------------------------------------
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
+ google_container_cluster.gcp_kubernetes
id: <computed>
additional_zones.#: "2"
additional_zones.1111111111: "australia-southeast1-b"
additional_zones.2222222222: ....... truncated
Plan: 1 to add, 0 to change, 0 to destroy.
------------------------------------------------------------------------
This plan was saved to: demo-k8s-gke.state
To perform exactly these actions, run the following command to apply:
terraform apply "demo-k8s-gke.state"
terraform apply
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
Outputs:
gcp_cluster_endpoint = xx.yyy.zzz.aa
gcp_cluster_name = hugocn
gcp_ssh_command = ssh [email protected]
google_container_cluster.gcp_kubernetes: Creating...
additional_zones.#: "" => "2"
additional_zones.1111111111: "" => "australia-southeast1-b"
additional_zones.2222222222: ....... truncated
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
Outputs:
gcp_cluster_endpoint = xx.yyy.zzz.aa
gcp_cluster_name = hugocn
gcp_ssh_command = ssh [email protected]
➜ # terraform -version
Terraform v0.11.2
+ provider.google v1.4.0
# terraform destroy
google_container_cluster.gcp_kubernetes: Refreshing state... (ID: hugocn)
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
- destroy
Terraform will perform the following actions:
- google_container_cluster.gcp_kubernetes
Plan: 0 to add, 0 to change, 1 to destroy.
Do you really want to destroy?
Terraform will destroy all your managed infrastructure, as shown above.
There is no undo. Only 'yes' will be accepted to confirm.
Enter a value: yes
google_container_cluster.gcp_kubernetes: Destroying... (ID: hugocn)
....... truncated
Destruction complete after 1m14s
Destroy complete! Resources: 1 destroyed.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent