Please note - these are meant to be used as examples for specific usecases. In general, we don't advise using these charts as-is for most environments, but figured they were worth sharing given the amount of effort we put into it!
- kubectl installed
- helm installed (requires
kubectl
) - Your local kubeconfig set up to talk to your K8s cluster
- Our private helm repo needs to be installed (hosted on in this repo!)
- We're following this process... mostly
- Add the helm chart to your local repos list:
helm repo add id-public "https://raw.githubusercontent.com/introspectdata/helm-public/master/"
This project has a bit of an 'odd' CI workflow through CircleCI:
- Only commits to master trigger builds
- Within that build, each individual chart needs to be specified in the build configuration
- If you're adding a new chart--make sure you update the build!
- This specific build profile has it's SSH deploy key set to read/write - so once it lints, packages and re-indexes the helm repo, it pushes to github again
- VERY IMPORTANT - the comment of the commit from CircleCI has a
[skip ci]
directive that makes it so that it doesn't loop infinitely.
- VERY IMPORTANT - the comment of the commit from CircleCI has a
helm repo index . --merge index.yaml
wget https://storage.googleapis.com/kubernetes-helm/helm-v2.9.1-linux-amd64.tar.gz -O /tmp/helm.tar.gz
sudo tar xvf /tmp/helm.tar.gz -C /usr/local/bin/ --strip 1
rm -rf /tmp/helm.tar.gz