https://lintech.uk/tags/kubernetes/Recent content in Kubernetes on Richard LinternHugo -- gohugo.ioen-GBCopyright © 2026 Richard LinternTue, 08 Sep 2026 19:23:00 +0100https://lintech.uk/projects/lintech-local-ai-platform/Tue, 08 Sep 2026 09:00:00 +0100https://lintech.uk/projects/lintech-local-ai-platform/Building a local-first AI platform that begins with a proven open model while establishing the data, architecture, training and evaluation foundations for an original Lintech language model.https://lintech.uk/lab-notes/gitops/flux-controller-health/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/gitops/flux-controller-health/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Basic controller health check: approximately 5 to 10 minutes</li> <li>Source or reconciliation investigation: approximately 15 to 30 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Use this entry when Flux resources are not reconciling, a source is stale, or one of the controllers appears unhealthy.</p>https://lintech.uk/lab-notes/gitops/kustomization-troubleshooting/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/gitops/kustomization-troubleshooting/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial Kustomization checks: approximately 5 to 10 minutes</li> <li>Build or dependency investigation: approximately 15 to 30 minutes</li> <li>Render, dry-run and reconciliation validation: approximately 20 to 45 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Use this entry when a Flux Kustomization is not ready, reports a build failure, waits on a dependency, or applies an unexpected revision.</p>https://lintech.uk/lab-notes/gitops/flux-reconciliation/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/gitops/flux-reconciliation/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Basic Flux health check: approximately 5 to 10 minutes</li> <li>Failed reconciliation investigation: approximately 10 to 30 minutes</li> <li>Render, dry-run, reconciliation and validation: approximately 15 to 45 minutes</li> </ul> <p>The actual duration depends on repository size, deployment dependencies, controller health and the cause of any reconciliation failure.</p>https://lintech.uk/lab-notes/gitops/gitops-repository-structure/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/gitops/gitops-repository-structure/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Repository orientation: approximately 5 to 10 minutes</li> <li>Planning a new component: approximately 15 to 30 minutes</li> <li>Reviewing an existing layout: approximately 20 to 45 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>This entry describes a practical GitOps repository structure that separates desired state, cluster registration, operational documentation and historical evidence.</p>https://lintech.uk/lab-notes/kubernetes/node-health-resource-pressure/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/kubernetes/node-health-resource-pressure/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial node triage: approximately 5 to 10 minutes</li> <li>Resource-pressure investigation: approximately 15 to 30 minutes</li> <li>Host-level investigation: approximately 20 to 45 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Use this entry when a node is <code>NotReady</code>, workloads cannot schedule, resource pressure is suspected, or platform capacity needs review.</p>https://lintech.uk/lab-notes/kubernetes/persistent-volume-checks/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/kubernetes/persistent-volume-checks/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial checks: approximately 10 to 20 minutes</li> <li>Detailed investigation: approximately 20 to 60 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Investigate PersistentVolumes, claims, storage classes, attachments and mount failures.</p>https://lintech.uk/lab-notes/kubernetes/pod-workload-troubleshooting/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/kubernetes/pod-workload-troubleshooting/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial pod triage: approximately 5 to 10 minutes</li> <li>Restart or scheduling investigation: approximately 15 to 30 minutes</li> <li>Dependency or storage investigation: approximately 30 to 60 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Use this entry to investigate pods in <code>Pending</code>, <code>Failed</code>, <code>Unknown</code>, <code>CrashLoopBackOff</code>, <code>ImagePullBackOff</code> or repeated restart states.</p>https://lintech.uk/lab-notes/kubernetes/resource-requests-limits/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/kubernetes/resource-requests-limits/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial checks: approximately 10 to 20 minutes</li> <li>Detailed investigation: approximately 20 to 60 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Review Kubernetes CPU and memory requests, limits, live usage and scheduling impact.</p>https://lintech.uk/lab-notes/kubernetes/longhorn-storage-health/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/kubernetes/longhorn-storage-health/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial checks: approximately 10 to 20 minutes</li> <li>Detailed investigation: approximately 20 to 60 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Check Longhorn workloads, volumes, replicas, nodes, capacity and warning events.</p>https://lintech.uk/lab-notes/gitops/sops-age-workflow/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/gitops/sops-age-workflow/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Validate an existing encrypted Secret: approximately 5 to 10 minutes</li> <li>Create and reconcile a new encrypted Secret: approximately 15 to 30 minutes</li> <li>Investigate a decryption fault: approximately 20 to 45 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>This entry describes a safe workflow for storing encrypted Kubernetes Secret manifests in Git using SOPS and age, with Flux performing decryption during reconciliation.</p>https://lintech.uk/lab-notes/kubernetes/cluster-health-checks/Sun, 30 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/kubernetes/cluster-health-checks/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial cluster triage: approximately 10 to 20 minutes</li> <li>Standard health review: approximately 30 minutes</li> <li>Full platform, storage and host review: approximately 30 to 60 minutes</li> </ul> <p>The actual duration depends on cluster size, access availability and whether any checks identify faults that need further investigation.</p>https://lintech.uk/projects/cloudflare-edge-hardening/Fri, 28 Aug 2026 09:00:00 +0100https://lintech.uk/projects/cloudflare-edge-hardening/A tunnel-based public access design with two cloudflared replicas, selective edge controls and CrowdSec-informed enforcement.https://lintech.uk/projects/observability-platform/Mon, 24 Aug 2026 09:00:00 +0100https://lintech.uk/projects/observability-platform/A website-like internal operations portal that unifies live telemetry from eleven validated APIs without replacing authoritative tools.https://lintech.uk/projects/longhorn-storage-recovery/Fri, 21 Aug 2026 09:00:00 +0100https://lintech.uk/projects/longhorn-storage-recovery/A layered recovery system combining Longhorn replication, daily snapshots, weekly QNAP backups and Veeam tape archival.https://lintech.uk/projects/sops-age-secret-management/Tue, 18 Aug 2026 09:00:00 +0100https://lintech.uk/projects/sops-age-secret-management/Encryption and recovery controls for 31 Git-managed Kubernetes Secret manifests using SOPS, age and Flux.https://lintech.uk/projects/flux-gitops-platform/Sun, 09 Aug 2026 09:00:00 +0100https://lintech.uk/projects/flux-gitops-platform/A declarative delivery system using Flux, Kustomize, Helm, image automation and encrypted Git-managed secrets.https://lintech.uk/projects/k3s-cluster/Sun, 12 Jul 2026 09:00:00 +0100https://lintech.uk/projects/k3s-cluster/A power-efficient, highly available four-node Kubernetes platform built with Raspberry Pi 5 hardware, k3s, Longhorn and GitOps.