zimmertr/kubernetes-manifests

A collection of my Kubernetes Manifests managed by Kustomize & ArgoCD

Kubernetes Manifests

• Summary
• Instructions
  • Networking
    • Istio
    • Cilium
  • Argo CD

---

Summary

This repository contains a collection of Kustomize projects and Argo CD resources used to deploy applications to Kubernetes.

Using Proxmox? Consider using TKS to deploy your cluster!

---

Instructions

Networking

Istio

Assuming you're using TKS with Flannel, Istio can be used to set up Metal LB & Istio:

# You may have to run this multiple times
kubectl kustomize istio/metallb | kubectl apply -f-
kubectl kustomize --enable-helm istio | kubectl apply -f-
kubectl kustomize --enable-helm istio-gateway | kubectl apply -f-

Cilium

Assuming you're using TKS and have disabled Flannel, Cilium) Can be used to install Cilium and Gateway API:

kubectl kustomize --enable-helm cilium/gateway-api | kubectl apply -f-
kubectl kustomize --enable-helm cilium/cilium | kubectl apply -f-
kubectl kustomize --enable-helm misc/kubelet-csr-approver | kubectl apply -f-

---

Argo CD

Argo CD is deployed manually at first using the same Kustomize pattern:

kubectl kustomize --enable-helm argo/argo-cd | kubectl apply -f-

Then you can apply ApplicationSets for a group of applications. For example:

kubectl apply -f argo/applicationset.yml

kubernetes-manifests's Issues

Set up Block Storage

Ideal storage would be Ceph, but I only have a single node so cannot forum a quorum. Wait for Longhorn support?

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency metallb/metallb to v0.14.7
• chore(deps): update helm release metrics-server to v3.12.1
• chore(deps): update linuxserver/sonarr docker tag to v4.0.8
• chore(deps): update ghcr.io/gethomepage/homepage docker tag to v0.9.5
• chore(deps): update helm release argo-cd to v6.11.1
• chore(deps): update helm release argo-rollouts to v2.37.2
• chore(deps): update helm release argo-workflows to v0.41.11
• chore(deps): update helm release base to v1.22.3
• chore(deps): update helm release cert-manager to v1.15.1
• chore(deps): update helm release cni to v1.22.3
• chore(deps): update helm release gateway to v1.22.3
• chore(deps): update helm release istiod to v1.22.3
• chore(deps): update helm release kube-prometheus-stack to v56.21.4
• chore(deps): update helm release kubelet-csr-approver to v1.2.2
• chore(deps): update helm release plex-media-server to v0.4.0
• chore(deps): update linuxserver/radarr docker tag to v5.8.3
• chore(deps): update nginx/nginx-prometheus-exporter docker tag to v1.2.0
• chore(deps): update proxmox-csi-plugin docker tag to v0.2.5
• chore(deps): update tautulli/tautulli docker tag to v2.14.3
• chore(deps): update helm release argo-cd to v7
• chore(deps): update helm release kube-prometheus-stack to v61
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

kustomize

argo/argo-cd/kustomization.yml

• argo-cd 6.0.14

argo/argo-rollouts/kustomization.yml

• argo-rollouts 2.34.3

argo/argo-workflows/kustomization.yml

• argo-workflows 0.40.10

istio/istio-gateway/kustomization.yml

• gateway 1.20.3

istio/istio/kustomization.yml

• base 1.20.3
• cni 1.20.3
• istiod 1.20.3

istio/metallb/kustomization.yml

• metallb/metallb v0.14.3

media/plex-media-server/kustomization.yml

• plex-media-server 0.2.0

media/radarr/kustomization.yml

• linuxserver/radarr 5.2.6

media/rutorrent/kustomization.yml

• crazymax/rtorrent-rutorrent 4.2.9-0.9.8-0.13.8

media/sonarr/kustomization.yml

• linuxserver/sonarr 4.0.1

media/tautulli/kustomization.yml

• tautulli/tautulli v2.13.4

misc/homepage/kustomization.yml

• ghcr.io/gethomepage/homepage v0.8.8

misc/kubelet-csr-approver/kustomization.yml

• kubelet-csr-approver 1.0.7

observability/kube-prometheus-stack/kustomization.yml

• kube-prometheus-stack 56.6.2

observability/metrics-server/kustomization.yml

• metrics-server 3.12.0

observability/nginx-prometheus-exporter/kustomization.yml

• nginx/nginx-prometheus-exporter 1.1.0

public/cert-manager/kustomization.yml

• cert-manager v1.14.2

public/personal-website/kustomization.yml

storage/nfs-subdir-provisioner/kustomization.yml

• nfs-subdir-external-provisioner 4.0.18

storage/proxmox-csi-plugin/kustomization.yml

• proxmox-csi-plugin 0.1.15

---

• Check this box to trigger a request for Renovate to run again on this repository

NFS Provisioner sets all StorageClasses as default

This is problematic because K8s wants you to have one default.

Add Infro PR Checks?

I noticed that this repo uses Argo CD, and I thought I’d let you know that I recently released a Github app called Infro that several companies use internally that allows Argo CD users to preview Kubernetes changes in Github pull requests before they merge. I’m providing it for free to open source projects (here’s an example in the wild). Here’s a setup guide with links to documentation. It’s in early stages, so I’m sure there will be warts. All feedback is welcome!

ruTorrent container image by Linuxserver is deprecated

Update to the crazy-max alternative

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: .github/renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: Configuration option prConcurrentLimit should be an integer. Found: "0" (string), Configuration option prHourlyLimit should be an integer. Found: "0" (string)

Unifi-Controller manifest deployment issue

failed: [pluto.local.lan] (item=dep_unifi_controller_mongodb.yml.j2) => {"ansible_loop_var": "item", "changed": false, "error": 400, "item": "dep_unifi_controller_mongodb.yml.j2", "msg": "Failed to create object: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Deployment in version \"v1\" cannot be handled as a Deployment: v1.Deployment.ObjectMeta: v1.ObjectMeta.Labels: ReadString: expects \" or n, but found 3, error found in #10 byte of ...|ersion\": 3.6, \"type\"|..., bigger context ...|\", \"app\": \"unifi-controller-mongodb\", \"version\": 3.6, \"type\": \"third-party\"}, \"namespace\": \"unifi-co|...","reason":"BadRequest","code":400}\n", "reason": "Bad Request", "status": 400}
failed: [pluto.local.lan] (item=dep_unifi_controller.yml.j2) => {"ansible_loop_var": "item", "changed": false, "error": 400, "item": "dep_unifi_controller.yml.j2", "msg": "Failed to create object: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Deployment in version \"v1\" cannot be handled as a Deployment: v1.Deployment.ObjectMeta: v1.ObjectMeta.Labels: ReadString: expects \" or n, but found 5, error found in #10 byte of ...|ersion\": 5.9, \"type\"|..., bigger context ...|internal\", \"app\": \"unifi-controller\", \"version\": 5.9, \"type\": \"third-party\"}, \"namespace\": \"unifi-co|...","reason":"BadRequest","code":400}\n", "reason": "Bad Request", "status": 400}