The notebook · 6 entries

Field notes.

Written after the fix, while the details are still fresh. Each note follows one question down through the layers: what the symptom said, which boundary was really at fault, and what I would check first next time.

Follow via RSS
Survey of the notebook

Every core sample.

  • WireGuard
  • OpenSSL
  • FluxCD
  • Gateway API
  • CI/CD
  • etcd
  1. NET-017

    When the tunnel is up but traffic is dead

    A WireGuard handshake proves that peers can exchange encrypted control traffic. It does not prove that application packets have a working path.

    • WireGuard
    • nftables
    • Linux networking
    2 min read
  2. PKI-009

    Building trust from the root up

    PKI becomes easier to reason about when it is treated as trust-chain and lifecycle design, not as a sequence of certificate-generation commands.

    • OpenSSL
    • X.509
    • CRL
    • TLS
    2 min read
  3. K8S-031

    Delivery as reconciliation

    GitOps is most useful when desired state, reconciliation order, and ownership boundaries are explicit enough to operate under failure.

    • FluxCD
    • Helm
    • Kustomize
    • GitOps
    2 min read
  4. EDGE-012

    Ingress is a routing problem

    Ingress failures become tractable when DNS, TLS, edge reachability, controller routing, service discovery, and workload health are tested as one path.

    • Gateway API
    • Istio
    • Traefik
    • DNS
    2 min read
  5. CI-024

    One pipeline primitive, many languages

    Reusable CI should standardize security and delivery behavior across languages while leaving language-specific build logic explicit.

    • CI/CD
    • Reusable workflows
    • Supply chain
    2 min read
  6. OPS-044

    Restore is not recovery until the cluster agrees

    Restoring etcd data is one step in Kubernetes recovery; control-plane identity, manifests, endpoints, certificates, and reconciliation still have to agree.

    • etcd
    • Kubernetes
    • Recovery
    2 min read