<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Zachary Volpi</title><description>Architecture decisions for software and platform systems, with a focus on performance, observability, and operability.</description><link>https://zvolpi.ch/</link><item><title>Designing a Staged Installation Topology with Flux</title><link>https://zvolpi.ch/posts/operations/designing-a-staged-installation-topology-with-flux/</link><guid isPermaLink="true">https://zvolpi.ch/posts/operations/designing-a-staged-installation-topology-with-flux/</guid><description>How to structure a Flux-managed cluster installation in clear stages so dependencies stay explicit, failures stay visible, and the topology stays replayable.</description><pubDate>Sat, 28 Feb 2026 22:55:00 GMT</pubDate></item><item><title>Designing the Promotion Metadata Contract for OCI-Backed Flux</title><link>https://zvolpi.ch/posts/operations/designing-the-promotion-metadata-contract-for-oci-backed-flux/</link><guid isPermaLink="true">https://zvolpi.ch/posts/operations/designing-the-promotion-metadata-contract-for-oci-backed-flux/</guid><description>How to define a promotion metadata contract that makes OCI-backed Flux delivery auditable, rollbackable, and understandable in production.</description><pubDate>Sat, 28 Feb 2026 19:10:00 GMT</pubDate></item><item><title>Floating Environment Tags vs Immutable References for OCI-Backed Flux Promotions</title><link>https://zvolpi.ch/posts/architecture-decisions/floating-environment-tags-vs-immutable-references-for-oci-backed-flux-promotions/</link><guid isPermaLink="true">https://zvolpi.ch/posts/architecture-decisions/floating-environment-tags-vs-immutable-references-for-oci-backed-flux-promotions/</guid><description>Choosing whether OCI-backed Flux promotions should target floating environment tags or immutable references, with pipeline-governed tag movement and digest-backed audit as the key constraint.</description><pubDate>Sat, 28 Feb 2026 18:15:00 GMT</pubDate></item><item><title>Observability of Flux Delivery Paths: Git, OCI, and Failure Visibility in Production</title><link>https://zvolpi.ch/posts/operations/observability-of-flux-delivery-paths-git-oci-and-failure-visibility-in-production/</link><guid isPermaLink="true">https://zvolpi.ch/posts/operations/observability-of-flux-delivery-paths-git-oci-and-failure-visibility-in-production/</guid><description>How to make Flux delivery paths observable in production: correlate Git or OCI source state, promotions, reconciliation, and rollout outcomes to explain failures quickly.</description><pubDate>Sun, 22 Feb 2026 21:26:33 GMT</pubDate></item><item><title>What a Kubernetes Delivery Path Actually Is (with Flux)</title><link>https://zvolpi.ch/posts/foundations/what-a-kubernetes-delivery-path-actually-is-with-flux/</link><guid isPermaLink="true">https://zvolpi.ch/posts/foundations/what-a-kubernetes-delivery-path-actually-is-with-flux/</guid><description>A Flux-aware mental model for Kubernetes delivery paths: control plane vs data plane, team ownership boundaries, promotion flow, and failure visibility.</description><pubDate>Sun, 22 Feb 2026 14:00:00 GMT</pubDate></item><item><title>GitOps vs GitlessOps (OCI) for Kubernetes Delivery with Flux</title><link>https://zvolpi.ch/posts/architecture-decisions/gitops-vs-gitlessops-oci-with-flux/</link><guid isPermaLink="true">https://zvolpi.ch/posts/architecture-decisions/gitops-vs-gitlessops-oci-with-flux/</guid><description>Choosing whether Flux should reconcile Kubernetes delivery state from Git or OCI artifacts, with trade-offs in promotion, observability, rollback, and operational burden.</description><pubDate>Sun, 22 Feb 2026 12:00:00 GMT</pubDate></item></channel></rss>