This draft keeps the operations side of a monitoring rollout intact: install kube-prometheus, expose the main services, add alerting configuration, and adjust the RBAC when the cluster needs broader access than the defaults provide.
This draft captures the practical flow for building a bare-metal Kubernetes cluster with MAAS and DeepOps: commission the nodes, deploy the operating system, prepare the inventory, tune the Kubernetes variables for the environment, and run the cluster build with enough observability to make the result usable.
This draft turns a raw build note into a practical cluster setup guide: wipe the storage disks carefully, prepare the network, deploy Kubernetes with DeepOps, add MetalLB, and leave the cluster in a state where Ceph and monitoring can be layered on cleanly.
This draft captures a practical bare-metal monitoring setup: install kube-prometheus, remove or adjust the network policies that block outside access, add MetalLB, convert the services to LoadBalancer, and patch the RBAC where the stock install is not enough for the cluster.
This draft captures the architecture and operational flow of a FusionAuth cluster build: prepare the Kubernetes base, add MetalLB, deploy PostgreSQL, choose and validate the search backend, and work through the application-side dependency checks before trying to restore or migrate real data.
This draft keeps the useful part of a migration note intact: back up the old Uptime Kuma data, install the chart, restore the data into the new deployment, switch the service to LoadBalancer, and verify the endpoint from outside the cluster.
This draft turns a storage incident note into a troubleshooting pattern: reproduce the issue with a minimal PVC and pod, inspect the events and Longhorn volume state, and use that evidence to separate application problems from storage attachment problems.
This draft captures a real troubleshooting pattern for 504 Gateway Timeout responses behind Kubernetes ingress by checking the ingress rule, backend service, pod health, and in-cluster connectivity from the ingress controller itself.
This draft captures a real ingress debugging flow on a bare-metal cluster: verify the service IP, inspect the ingress objects, deal with a Helm ownership conflict, reinstall the controller cleanly, and confirm that the new ingress class is actually serving the expected backend.
This draft walks through the practical flow for connecting an existing Ceph cluster to Kubernetes with Rook: collect the monitor data and FSID, generate external-cluster resources, import them into the target cluster, install the Rook operator, and verify that the external Ceph connection is healthy.