jgreat

Set up a 3 node HA rancher cluster.

This will create and prep nodes for RKE. This uses the default vpc and subnets.

We create:

• SSH Key Pair
• Security Groups
• 3 Instances
• ELB for 80/443 points to the 3 instances.

jgreat

docker rm -fv $(docker ps -qa)
docker volume ls -q | xargs docker volume rm
rm -rf /etc/ceph \
       /etc/cni \
       /etc/kubernetes \
       /opt/cni \
       /opt/rke \
       /run/secrets/kubernetes.io \
       /run/calico \
       /run/flannel \

jgreat

CA

First we need to generate a CA for signing the website certs.

Generate CA Private Key

openssl genrsa -out ca.key 2048

jgreat

storageClass with PersistentVolumeClaims are really the way to do storage with Kubernetes.

For Azure There are 3 types of storage avalible.

• (Slow, Limited, Going to cause tears) AzureFiles - CIFS share, with all the limitaions of CIFS :(
• (Better) Azure Disk (Storage Account) - You can use this type with Azure "Node Driver" VMs in Rancher.
• (Best) Azure Disk (Managed) - You will need to create your own VMs that support managed disk with premium storage, then use the "Custom" option.

jgreat

Prerequisits

Describe installs for.

• rke
• kubectl
• helm

jgreat

MySQL Config Tuning

Connections:

First and foremost it is important to not run out of connections from the Rancher Server to the MySQL database server. The threads per server are driven by the thread pool size. So max connections should follow this basic formula:

Number of nodes x Total threads + buffer for non-rancher tasks

• Number of nodes: Rancher Management server nodes.
• Total Threads: Sum of all thread pools (maximums) found on (http(s):///admin/processes/pools). Default: 150
• Buffer: Non-rancher tasks such as monitoring, admin, backups and other ad hoc tasks require connections as well.

jgreat

Azure Node Driver

Create an cluster with an existing vnet/subnet in your subscription

Credentals

You need to set up an app access (service principal): https://rancher.com/docs/rancher/v1.6/en/hosts/azure/#app-registration

Vnet/Subnet

jgreat

Install with custom script

AMI:

• Ubuntu Server 16.04 - ami-91659f4

Size:

• t2.medium

jgreat

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  creationTimestamp: null
  labels:
    run: server
  name: server
spec:
  replicas: 1
  selector:

jgreat

#!/bin/bash

### kubectl should really allow you to export a singel context.
### if you only have one context you can just run `kubectl config view --flatten`
### if you have more than one context use this script.
###
### **Requires jq: https://stedolan.github.io/jq/
###

context=${1:-"minikube"}