scottrigby

GitOps for Helm Users

Outline

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

carolynvs

[alias]
  wip = for-each-ref --sort='authordate:iso8601' --format=' %(color:green)%(authordate:relative)%09%(color:white)%(refname:short)' refs/heads
  

tegioz

package main

import (
	"context"
	"flag"
	"fmt"
	"io/ioutil"
	"net/http"
	"strings"

jonsamp

#!/bin/bash
sudo bash -c 'cat << 'EOF' >> /Applications/Slack.app/Contents/Resources/app.asar.unpacked/src/static/ssb-interop.js
document.addEventListener("DOMContentLoaded", function() {
 $.ajax({
   url: "https://cdn.rawgit.com/laCour/slack-night-mode/master/css/raw/black.css",
   success: function(css) {
     let overrides = \`
     code { background-color: #535353; color: #85c5ff; } /* Change color: to whatever font color you want */
     .c-mrkdwn__pre, .c-mrkdwn__quote { background: #535353 !important; background-color: #535353 !important; }
     \`

scottrigby

FROM bitnami/drupal:8

COPY custom-app-entrypoint.sh /

ENTRYPOINT ["/custom-app-entrypoint.sh"]
CMD ["/run.sh"]

scottrigby

FROM bitnami/drupal:8

# Allow user codebase to include a custom composer merge file.
# See https://github.com/wikimedia/composer-merge-plugin.
COPY merge-composer.json /opt/bitnami
RUN apt-get update && apt-get install -y jq
RUN cd /opt/bitnami/drupal \
    && tmp=$(mktemp) \
    && cat composer.json | jq '.extra."merge-plugin".include |= .+ ["../merge-composer.json"]' > "$tmp" \
    && mv "$tmp" composer.json \

scottrigby

#!/bin/sh

# See https://github.com/kubernetes/helm/blob/master/docs/rbac.md#tiller-and-role-based-access-control

echo 'apiVersion: v1
kind: ServiceAccount
metadata:
  name: tiller
  namespace: kube-system
---

scottrigby

#!/bin/bash
echo 'Why did the guy get fired from the orange juice factory?'; read ANSWER;
echo "He couldn’t concentrate! 🍊😂😭. But '${ANSWER}' is funny too."

mattfarina

Hosted Chart Repository Requirements

Background

Kubernetes Helm has the ability to work with remotely hosted Charts. While charts can be seen in the community provided charts, the charts themselves can be privately or separately hosted for an organization or individual.

There are currently 3 major ways to host your own chart repository:

• Helm provides a means to generate a chart repository that can be hosted on a web server, object storage, or via a similar setup.
• App Registry provides a system, similar to the handling of Docker images, to store charts. In this setup one can push or pull charts in a similar way to container images. There is a spec and Quay, the image hosting service, has implemented it. For Helm to interact with this API a plugin is required.

scottrigby

#!/bin/bash

# @file
# See HELP().
# This script is useful until functionality is adopted into Helm.
#
# Follow @link https://github.com/kubernetes/helm/issues/1947 the issue. @endlink

# Define SCRIPT var for help and validation output.
SCRIPT=`basename ${BASH_SOURCE[0]}`