traefik

Uptime-Kuma is a self-hosted monitoring tool that gains more and more popularity on GitHub. This post describes how to deploy the Uptime-Kuma on Kubernetes. Use the following StatefulSet to deploy Uptime-Kuma: # StatefulSet apiVersion: apps/v1 kind: StatefulSet metadata: name: uptime-kuma namespace: monitoring spec: replicas: 1 serviceName: uptime-kuma-service selector: matchLabels: app: uptime-kuma template: metadata: labels: app: uptime-kuma spec: containers: - name: uptime-kuma image: louislam/uptime-kuma env: - name: UPTIME_KUMA_PORT value: "3001" - name: PORT value: "3001" ports: - name: uptime-kuma containerPort: 3001 protocol: TCP volumeMounts: - name: uptime-kuma-data mountPath: /app/data volumeClaimTemplates: - metadata: name: uptime-kuma-data spec: accessModes: ["ReadWriteOnce"] volumeMode: Filesystem resources: requests: storage: 2Gi storageClassName: <your-storage-class> Make sure to enter a storage class you want to use....

Traefik is a modern reverse proxy and load balancer that makes deploying microservices easy. Traefik is natively compliant with Kubernetes, Docker and a lot of other cluster technologies. Traefik allows the use of middlewares to tweak requests before they are sent to a service. There are several available middlewares in Traefik, some can modify the request, the headers, some are in charge of redirections and some add authentication. This Post explains how to configure the BasicAuth-Middleware for Traefik 2 in Kubernetes....