Chris Carmichael Chris-Carmichael

Please check https://aws.github.io/aws-eks-best-practices/ for more comprehensive EKS best practice!

Architecture

Think about multi-tenancy, isolation for different environment or different workload
- Isolation at account level using AWS organization
- Isolation at the network layer ie. different VPC & different cluster
- Use different Nodes Group (Node pool) for different purpose/category e.g. create dedicated node groups for Operational tools such as CI/CD tool, Monitoring tool, Centralize logging system.
- Separate namespace for different workload

Reliability | Principles

Awesome Piracy

A curated list of arrrrrrrrr!

Kubernetes cheatsheet

Kubernetes cheatsheet
Everything is an object - persistent entities

My Openshift Cheatsheet

Openshift Secrets

"There are different secret types which can be used to enforce usernames and keys in the secret object: service-account-token, basic-auth, ssh-auth, tls and opaque. The default type is opaque. The opaque type does not perform any validation, and allows unstructured key:value pairs that can contain arbitrary values.

Data is stored inside a secret resource using base64 encoding. When data from a secret is injected into a container, the data is decoded and either mounted as a file, or injected as environment variables inside the container."

To create ssh secret:

	#!/usr/bin/env bash

	export CLUSTER_NAME="ruzickap-cilium"
	export AWS_DEFAULT_REGION="eu-central-1"
	export KUBECONFIG="/tmp/kubeconfig-${CLUSTER_NAME}.conf"

	export TAGS="[email protected] Environment=dev Group=Cloud_Native Squad=Cloud_Container_Platform"

	set -euxo pipefail

	#!groovy
	import groovy.json.JsonOutput
	import groovy.json.JsonSlurper

	def label = "mypod-${UUID.randomUUID().toString()}"
	podTemplate(label: label, yaml: """
	spec:
	containers:
	- name: mvn
	image: maven:3.3.9-jdk-8