StevenACoffman

# Alex Ellis 2018
# Example from: https://blog.alexellis.io/quick-look-at-google-kaniko/

# Pre-steps:
# kubectl create secret generic docker-config --from-file $HOME/.docker/config.json

# Other potential optimizations (suggested by @errordeveloper)
# - Store "templates" in a permanent volume
# - Download source via "tar" instead of git clone

StevenACoffman

From Twitter by Doc Norton (@DocOnDev)

A: How long will it take to build this simple feature?
B: Well, how should this part work?
A: We don't know yet.
B: And in this situation...?
A: We don't know yet.
B: And Here?
A: We don't know yet.

StevenACoffman

From https://aws.amazon.com/blogs/opensource/integrating-ldap-ad-users-kubernetes-rbac-aws-iam-authenticator-project/

3. Configure Role Permissions via Kubernetes RBAC

At this point, we have set up Microsoft AD to control authentication to the AWS SSO user portal. We have also set up partial authorization by specifying which AD group has been assigned access to Account B (where the EKS cluster resides). However, access control (i.e., the level of permissions granted to the AD users) has not yet been specified. In this section, we will demonstrate how Kubernetes RBAC can be configured to define access control for AD users/groups via federation through an AWS IAM role.

Before proceeding with the steps below, be sure that that:

1. You have a working Kubernetes cluster with worker nodes.

StevenACoffman

Argo vs. Brigade some of the key differences are

• K8s CRD vs. javascript execution service

• Declarative YAML vs. javascript

• Argo has built-in artifact support for input/output handling

• Argo does not have event handling yet (working on it :-)

  As of dec 2017

Argo vs Airflow

StevenACoffman

prometheus-operator/kube-prometheus#16 (comment) https://github.com/kayrus/prometheus-kubernetes/blob/master/alertmanager-configmap.yaml

StevenACoffman

#!/bin/bash -e

# NOTE: CHANGE THE S3_PREFIX!!!
# Add user to k8s 1.6+ using service account, RBAC for jobs and extensions only
if [[ -z "$1" ]] || [[ -z "$2" ]];then
 echo "usage: $0 <service-account> <namespace (stg|prod)>"
 exit 1
fi

SERVICE_ACCOUNT_NAME=$1

StevenACoffman

#!/bin/bash


# Check if a value exists in an array
# @param $1 mixed  Needle
# @param $2 array  Haystack
# @return  Success (0) if value exists, Failure (1) otherwise
# Usage: in_array "$needle" "${haystack[@]}"
# See: http://fvue.nl/wiki/Bash:_Check_if_array_element_exists
in_array() {

StevenACoffman

NAME   := acmecorp/foo
TAG    := $$(git log -1 --pretty=%!H(MISSING))
IMG    := ${NAME}:${TAG}
LATEST := ${NAME}:latest
 
build:
  @docker build -t ${IMG} .
  @docker tag ${IMG} ${LATEST}
 
push:

StevenACoffman

That being said, I think that, as engineers, we tend to discount the complexity we build ourselves vs. complexity we need to learn.

— Joe Beda

Don't spend more time discussing a reversible change than it would take to make (& potentially reverse) the change

— Kent Beck

StevenACoffman

package main

import (
	"log"

	"encoding/json"
	"fmt"
	"os"

	"math/rand"