Back to Feed
CI/CD with Robert Erez
The Signal
Modern CI/CD delivery is often misconstrued as a linear progression toward universal cloud-native adoption, but real-world reliability relies on a far more nuanced mix of on-prem orchestration, stateful migration strategies, and practical tool selection. The central tension pits the theoretical purity of dominant industry frameworks—like GitOps and continuous deployment—against the messy reality of regulated compliance, stateful schema management, and the unpredictable upgrade cadences of on-prem customers.
The Case
- Kubernetes is frequently used outside cloud environments, including research vessels at sea, financial institution data centers, and point-of-sale systems across hundreds of retail stores.
- GitOps is often burdened by dogmatism; the speaker argues that none of its four core pillars—declarative state, immutability, pull-based reconciliation, and continuous correction—actually require Git itself.
- Rollback is frequently a dangerous mental model for stateful systems, as code reversions often clash with newer database schema changes; the speaker emphasizes "rolling forward" with hotfixes instead.
- Feature toggles are often more practical for progressive delivery than canary or blue-green deployments, as they enable finer granularity and instantaneous remote off-switching without the redeployment latency of traditional traffic shaping.
- Supporting both SaaS and on-prem deployments creates a massive version-compatibility debt, with internal data showing typical on-prem customers take 200 days for 50% adoption of new changes, while others remain on 7-year-old versions.
- AI is expected to dramatically increase raw code volume, potentially shifting future CI/CD focus away from pipeline execution speed toward automated risk validation, observability, and robust feature-gating.
The 1 Minute Signal Take
This is a remarkably crisp take on infrastructure reality that cuts through the marketing fluff surrounding GitOps and cloud-native dogma. It is worth watching for the specific architectural insights on why stateful systems defy standard rollback logic and how the speaker balances SaaS resilience with the constraints of long-tail, self-hosted version support.
Time saved:
Tags
Back to Feed