...
- Federation - federation of multiple clusters in GKE and other providers is available
- Multi-zone clusters - nodes across failure-domains and regions
- registry - private local docker registry with code repository integration build triggering
- Logging via StackDriver - Enable when provisioning, access via main menu under stackdriver
- Monitoring via StackDriver - Enable when provisioning, access via main menu under stackdriver
- preemptible nodes can be used for parts of the cluster - but they are preemptible so can evaporate, so if there is preemptible workload,
save cost by allocating some preempitble nodes and place preemptible work there via labels, taints, or schduling affinity - IAM Oauth2.0 RBAC cluster access managemement - fine grained configuration of accounts→roles managed via GKE dashboard
- Auto-upgrade will keep bump k8's versions on masters automatically. Nodes can also be set to auto-upgrade or can be upgraded by hand.
- Master must be >= nodes always and version(master)-version(nodes) <= 2.x.x. A 1.5.3 master is compatible with (1.{3,4}.X, 1.5.3-)
- Must have enough capacity in cluster to evacuate pods from the node to other while a node is rolled to avoid unschedulable pods.
- Auto-upgrade can be rolled-back if necessary
- Auto cluster-scale - will automatically scale up/down the number of nodes in the cluster based on CPU/memory
- Node Auto-repair - will rebuild a node that has failed, does not become ready, or becomes unready due to crash.
...
Tests for WB fitness
- Tested/confirmed
- boot cluster
- deploy rc, scale up/dn (nginx)
- deploy svc (nginx)
- deploy ingress to svc nginx
- access via local GKE, access via browser from internet
- deploy privileged pod
- Not tested, unknown:
- blkdev access via privileged container to host blkdev
- hostnetwork