Single-node K3s is a pragmatic choice for homelabs and lightweight production workloads.
Single-node K3s is a pragmatic choice for homelabs and lightweight production workloads, offering Kubernetes compatibility without the overhead of multi-node clusters.
Use containerd directly with kaniko for building images and avoid DIND complexities.
Use containerd directly with kaniko for building images and avoid DIND complexities.
Use Velero for cluster state, Kube-state-metrics for workloads, and Rook/Ceph for storage.
Use Velero for cluster state, Kube-state-metrics for workloads, and Rook/Ceph for storage, but expect manual steps for dependencies and validation.
Internal Kubernetes storage for stateful services is viable for small-scale or isolated workloads but introduces complexity and.
Internal Kubernetes storage for stateful services is viable for small-scale or isolated workloads but introduces complexity and risk at larger scales.
Misconfiguring network policies to allow all traffic by default creates invisible security risks that go unnoticed until.
Misconfiguring network policies to allow all traffic by default creates invisible security risks that go unnoticed until exploited.
Preventative maintenance, routine care, and repairs for Kubernetes & OpenShift clusters
I’m a Red Hatter working as a Solutions Architect, formerly a Senior Cloud Success Architect, with a focus on and passion for OpenShift and Ansible. Previous life? Cloud Advanced Technology Lead & Big Data Engineer for Lockheed Martin Space, IT/IS Data Center Manager for Lockheed Martin IS&GS, and Senior Infrastructure Designer/Administrator for the City of Gainesville & City of Alachua.
Learn More
Share this post
Twitter
Google+
Facebook
Reddit
LinkedIn
StumbleUpon
Pinterest
Email