Scott Rigby scottrigby

setup
```
$ kind create cluster
```

install zot with minimal image for security-minded dist-spec-only

$ helm upgrade zot zot/zot --set image.repository=ghcr.io/project-zot/zot-minimal-linux-amd64

How to Structure GitOps Repos

Let's get started

$ tmp=`mktemp -d` && cd $tmp && pwd
/var/folders/7w/tx9gxzkd4p79y2nsj7b5dmdw0000gn/T/tmp.YvRWeerz

Set up simple monorepo directories, preview, and add all in one commit

GitOps for Helm Users

Outline

Install Flux CLI and Kind
Make Personal Access Token for creating repositories
Export env vars locally
Create local demo cluster
Simple bootstrap
Clone the newly created git repo to your local workspace
Lets create a Helm release the most common way, using the Helm CLI

Introduction to GitOps & The Flux Family of Projects

Set up local cluster and Flux CLI

Install Flux CLI and Kind:

$ brew reinstall flux kind
$ kind --version
kind version 0.11.1

Helm Users! What Flux 2 Can Do For You

This is the gist promised in our our KubeCon EU 2021 talk.

Go to https://github.com/kingdonb/kccnceu2021 for the full experience! 💖🤩

Check out the main branch for the full talk experience (warts and all)
Check out the present branch for the solutions according to the presenter
Check out the terminal branch for risky root shell fun
Check out the features branch for additional features as we incorporate them throughout the week based on your suggestions!

Flux use case: Cert Manager, Traefik, app with ingress, GitHub as source

Set up local cluster and Flux CLI

Install Flux CLI and Kind:

$ brew reinstall flux kind
$ kind --version
kind version 0.10.0

Hands-On GitOps Patterns for Helm Users

Install Flux CLI and Kind:

$ brew reinstall flux kind
$ kind --version
kind version 0.10.0
$ flux --version
flux version 0.9.1

⚠️ Work In Progress

Public Timetable for Flux 1 to 2 Migration & Support

Goal: A simple, memorable, canonical, public timetable to be used for community communication (READMEs, blog posts, etc), not for internal planning.

Purpose: State our commitment to end users to improve their experience in knowing how and when to plan their own infra decisions related to Flux.

When	Flux 2	Flux 1

	#! /bin/bash

	set -u
	# example: r6by/testoci
	: GITHUB_REPOSITORY

	yesno() {
	read -p "${1} (y/n)?" choice
	case "$choice" in
	y\|Y ) return 0;;

	tap "aquasecurity/trivy"
	tap "fluxcd/tap"
	tap "github/gh"
	tap "helm/tap"
	tap "homebrew/bundle"
	tap "homebrew/cask"
	tap "homebrew/core"
	tap "teamookla/speedtest"
	tap "weaveworks/tap"
	brew "bash-completion@2"