search

shabados / manifests

Manifests for continuous deployment to Kubernetes
GNU General Public License v3.0
0 stars 0 forks source link

readme

Shabad OS Manifests

This repo contains all the manifest files used by Flux to manage the state of the Shabad OS Kubernetes cluster.

Once Flux is correctly initialised, the cluster will synchronise itself into the state defined by the YAML manifest files.

Flux will also update the images and Helm charts to the latest versions and push the changes back to the repository.

Cluster Setup

Note: Use bash to execute these commands

Install Helm, create a flux namespace, install Flux with Helm, job done 😊.

Create Kubernetes Dashboard Permissions

Optional, if planning to use Kubernetes dashboard. This provides the correct permissions to the kubernetes dashboard account.

kubectl create clusterrolebinding kubernetes-dashboard --clusterrole=cluster-admin --serviceaccount=kube-system:kubernetes-dashboard

Install Helm

Install the Helm CLI.

On Windows: choco install kubernetes-cli kubernetes-helm

Create Flux namespace

Create a namespace dedicated to running flux:

kubectl create namespace flux

Install Flux

Ensure Helm is correctly installed.

To initialise or upgrade Flux in the cluster:

helm repo add fluxcd https://charts.fluxcd.io

helm upgrade -i flux \
--set helmOperator.create=true \
--set helmOperator.createCRD=true \
--set git.url=git@github.com:ShabadOS/manifests \
--set git.user="Shabad OS Bot" \
--set git.email="team@shabados.com" \
--namespace flux \
fluxcd/flux

Install the Flux Helm Operator and Helm Custom Resource Definition

Add the custom resource definition for Flux:

kubectl apply -f https://raw.githubusercontent.com/fluxcd/helm-operator/master/deploy/flux-helm-release-crd.yaml

helm upgrade -i helm-operator fluxcd/helm-operator \
--namespace flux \
--set helm.versions=v3 \
--set git.ssh.secretName=flux-git-deploy

Update the Sealed Secrets Public Key

Install the kubeseal CLI.

After the sealed-secrets chart has been spun up and deployed, retrieve and store the public key for the controller as secrets/pub-cert.pem, using the following command:

kubeseal --fetch-cert \
--controller-name=sealed-secrets \
--controller-namespace=kube-system \
> secrets/pub-cert.pem

Be sure to commit and push this to the repository.

Note: You must re-encrypt any secrets with the new sealed secrets public key.

Storing secrets

Install the kubeseal CLI.

In the secrets directory run:

kubectl -n [NAMESPACE] create secret generic \
  secret-name \
  --dry-run \
  --from-file=input.json \
  -o json > secret.tmp.json

kubeseal --format=yaml --controller-name=sealed-secrets -n [NAMESPACE] -- < secret.tmp.json > sealed-secret.yaml

Helm Releases

Workloads