Kops

stuff:

1. /bin/sh

1. Source:
2. https://kubernetes.io/docs/setup/custom-cloud/kops/
3. route 53 domain registered and hosted:

1. check existing status:

echo subdomain: ${subdomain} echo bucketconfig: ${bucketconfig} echo prefix ${prefix} echo cn: ${cn} echo pubkey ${pubkey}

export subdomain="dev.thedomain.com" export bucketconfig="dthornton-clusters" export prefix="lab001" export cn="${prefix}.${subdomain}" # clustername export pubkey="~/.ssh/dthornton.pub"

1. check again:

echo subdomain: ${subdomain} echo bucketconfig: ${bucketconfig} echo prefix ${prefix} echo cn: ${cn} echo pubkey ${pubkey}

1. does the bucket exist?

aws s3api list-buckets --output table | grep ${bucketconfig}.${subdomain}

1. if not make a bucket:

echo aws s3 mb s3://${bucketconfig}.${subdomain}

1. aws s3 mb s3://${bucketconfig}.${subdomain}

1. sync a local copy
2. aws s3 sync s3://${bucketconfig}.${subdomain} s3bucket

export KOPS_STATE_STORE="s3://${bucketconfig}.${subdomain}"

echo KOPS_STATE_STORE echo ${KOPS_STATE_STORE}

1. example:
2. kops create cluster --zones=us-east-1c useast1.dev.quadratic.net

1. cluster creation , chicken and egg:
2. this command makes the kops cluster object but fails to make all the aws cloud objects because there is no key to give the instances.

kops create cluster --zones="ca-central-1a,ca-central-1b" "${cn}"

kops create cluster \ --zones ca-central-1a,ca-central-1b \ --master-zones ca-central-1a \ --image ami-9526abf1 \ # latest ca-central-1 ubuntu Tue 18 Sep 2018 10:52:50 EDT --ssh-public-key ${pubkey} \ --node-size t2.medium \ --node-count 2 \ --master-size t2.medium \ --network-cidr 10.10.0.0/16 \ --dns-zone ${subdomain} \ --cloud-labels "owner=dthornton,managedby=kops" \ --name ${cn} \ --yes

kube config is : /Users/david/.kube/config

api url: https://api.${cn}/api/v1/nodes?limit=500

optional:

kops update cluster --name $cn --yes

Note that above we explicity tell it what public key to use at the outset.

1. now make a kube secret of type public key. This assumes you already have a private public pair and you are giving kops the public part so that it can give it to kubrnetes and AWS.

1. kops create secret --name ${cn} sshpublickey admin -i ~/.ssh/${pubkey}
2. kops edit cluster ${cn}

1. ig = instance group

kops edit ig --name=${cn} nodes kops edit ig --name=${cn} master-ca-central-1a

1. Suggestions:
2. * validate cluster: kops validate cluster
3. * list nodes: kubectl get nodes --show-labels
4. * ssh to the master: ssh -i ~/.ssh/id_rsa admin@api.cacentral.dev.quadratic.net
5. * the admin user is specific to Debian. If not using Debian please use the appropriate user based on your OS.
6. * read about installing addons at: https://github.com/kubernetes/kops/blob/master/docs/addons.md.

kops update cluster ${cn} --yes

kops rolling-update cluster

1. specify some stuff at creation:

1. kops create cluster \
2. --master-zones=us-east-1a,us-east-1b,us-east-1c \
3. --zones=us-east-1a,us-east-1b,us-east-1c \
4. --node-count=2 \
5. --image ami-32705b49 \
6. ${cn}

kubectl -n kube-system get po

set name spae to kube-system get pods

1. Note that the kops destroy cleans out the kubectl config file: "/Users/david/.kube/config"

kops delete cluster ${cn} --yes