This tutorial will walk you through building a Kubernetes cluster with Kops in AWS Beijing or NinXia Region.
Name | Support Kops Version | Support Kubernetes Version | Last Update |
---|---|---|---|
pahud/kops-bjs | 1.9.2 | 1.9.8 | July 24th, 2018 |
Prepare the AMI
Install Kops and Kubectl client on your laptop
Create a proxy server with gost in AWS N. Virginia Region
Create a proxy forwarder in AWS Beijing Region
Create the cluster with Kops
Check the latest AMI ID from Kops Images document and find the AMI ID in the global regions(e.g. N. Virginia).
However, as the China Beijing region already has latest CoreOS AMI, you can just check CoreOS official EC2 AMI page and select the AMI for cn-north-1
region, make sure you select the HVM
AMI type. For example, current AMI ID is ami-2a875e47 (Container Linux 1745.7.0). Please note the latest AMI ID may change over time.
Region | CoreOS AMI |
---|---|
Beijing(cn-north-1) | ami-2a875e47 |
NinXia(cn-northwest-1) | ami-c9abbfab |
click the button to create a proxy server with gost and AWS Fargate in any of the following regions.
Region | Launch Stack in VPC | Runtime |
---|---|---|
Oregon (us-west-2) | Fargate+ECS | |
N. Virginia (us-east-1) | Fargate+ECS |
Depending on which region you woud like to provision your Kops cluster, click the button below to create an internal http_proxy forwarder for your Kops cluster. This template will create one t2.micro EC2 behind ELB in your existing VPC as the proxy forwarder.
Region | Launch Stack in VPC | Runtime |
---|---|---|
Beijing (cn-north-1) | EC2+ELB | |
NinXia (cn-northwest-1) | EC2+ELB |
Depending on what region you intend to deploy your Kops, follow the fastboot guide
below to continue your setup.
Region | Guide |
---|---|
Beijing(cn-north-1) | fastboot guide |
NinXia(cn-northwest-1) | fastboot guide |
delete the cluster
$ kops delete cluster --name cluster.bjs.k8s.local --yes
And delete the two cloudformation stacks from N.Virginia
and Beijing
regions.
Questions? check the FAQ list here.