infrapuzzle/k8s
Moritz Graf 35f63edb42 Deployment of kuard demo successful in large parts. 2020-04-05 12:34:48 +02:00
..
blub Deployment of kuard demo successful in large parts. 2020-04-05 12:34:48 +02:00
cert-manager Cert-manager deployed 2020-04-05 10:17:47 +02:00
default Deployment of kuard demo successful in large parts. 2020-04-05 12:34:48 +02:00
nginx-ingress Deployment of kuard demo successful in large parts. 2020-04-05 12:34:48 +02:00
README.md Deployment of kuard demo successful in large parts. 2020-04-05 12:34:48 +02:00
busybox.yaml Cert-manager deployed 2020-04-05 10:17:47 +02:00

README.md

k8s

This folder holds all the services required for my private infrastructure. Following contraints apply:

  • Order of implementation is top down.
  • Every namespace has a subfolder within this subdirectory.
  • helm3

namespaces

k create ns flux
k create ns cert-manager
k create ns nginx-ingress
k create ns infrapuzzle

helm-operator

As I use helm extensively, using the helm-operator was a logical step. See documentation for installation.

$ helm repo add fluxcd https://charts.fluxcd.io
$ helm repo update
$ kubectl apply -f https://raw.githubusercontent.com/fluxcd/helm-operator/master/deploy/crds.yaml
$ helm upgrade -i helm-operator fluxcd/helm-operator \
    --namespace flux \
    --set helm.versions=v3

ingress-controller

Apply with helm-operator:

$ kubectl apply -f nginx-ingress/ingress.yaml

cert-manager

Apply with helm-operator:

$ kubectl apply -f https://raw.githubusercontent.com/jetstack/cert-manager/master/deploy/manifests/00-crds.yaml
$ kubectl apply -f cert-manager/cert-manager.yaml
$ kubectl apply -f cert-manager/staging-issuer.yaml
$ kubectl apply -f cert-manager/production-issuer.yaml