Skip to content

Instantly share code, notes, and snippets.

@rsmitty
rsmitty / demo.md
Last active October 21, 2020 18:50

Pre-setup

Create all docker mirrors

docker run -d -p 5000:5000 \
    -e REGISTRY_PROXY_REMOTEURL=https://registry-1.docker.io \
    --restart always \
    --name registry-docker.io registry:2.5
---
# Source: cilium/charts/agent/templates/serviceaccount.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
name: cilium
namespace: kube-system
---
# Source: cilium/charts/hubble-ui/templates/serviceaccount.yaml
apiVersion: v1
#!/bin/bash
## Vars to use for various things
CAPI_VERSION="0.2.10"
## Setup our directories
OUT_DIR="$PWD/_out"
TMP_BASE="$PWD"
TMP_DIR="$(mktemp -d -t _tmp-XXXXXXXXXX --tmpdir=$TMP_BASE)"
mkdir -p $OUT_DIR
@rsmitty
rsmitty / a.yaml
Last active January 13, 2020 20:31
apiVersion: v1
kind: ServiceAccount
metadata:
name: hwhat
namespace: default
---
apiVersion: v1
kind: Pod
metadata:
name: alpine
---
# Source: cilium/charts/config/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: cilium-config
namespace: kube-system
data:
# Identity allocation mode selects how identities are shared between cilium
---
kind: pipeline
name: default
steps:
- name: basic-integration
image: autonomy/build-container:latest
pull: always
commands:
- echo "this one always runs"
I AML tables successfully acquired and loaded
[ 1.059958] ACPI: Interpreter enabled
[ 1.060017] ACPI: (supports S0 S3 S5)
[ 1.061001] ACPI: Using IOAPIC for interrupt routing
[ 1.062070] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
@rsmitty
rsmitty / cluster-api-provider log
Last active May 7, 2019 16:43
Cluster API Provider Multi-machine actuator issue
$ kubectl logs -f -n cluster-api-provider-talos-system cluster-api-provider-talos-controller-manager-0
{"level":"info","ts":1557246922.364505,"logger":"talos-controller-manager.entrypoint","msg":"Adding machine actuator:","provisioner":{"Provisioner":{},"Clientset":{"LegacyPrefix":"/api"}}}
{"level":"info","ts":1557246922.3647182,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"machine-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1557246922.365611,"logger":"talos-controller-manager.entrypoint","msg":"Adding machine actuator:","provisioner":{"Provisioner":{},"Clientset":{"LegacyPrefix":"/api"}}}
{"level":"info","ts":1557246922.3657587,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"machine-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1557246922.365843,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"cluster-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1557246922
@rsmitty
rsmitty / gcrsearch.md
Last active September 1, 2016 17:35
GCR Tag Search

#####Add this to end of ~/.bash_profile:

gcrsearch() { curl -s "$1/tags/list" | jq '.manifest[].tag[]' | sort; }
alias gcrtags=gcrsearch

#####After opening a new term, use like:

Rolling Updates

Here's how a rolling update works:

  • A Deployment specification is created (YAML file), where labels are specified for Pods that will be created. In this example assume app:nginx, tier:frontend, version:1.0.

  • A strategy of RollingUpdate is also specified

  • The Deployment is created with kubectl create -f deployment.yaml