Exclude Human – Continuous Deployment and OpenShift
summary
Company shifts from multi-day, manual releases to daily or several-times-per-day automated deploys by replacing VMs with a container orchestrator and building OpenShift clusters, Ansible playbooks and Jenkins pipelines that create dynamic preview environments per pull request. Stateful sets use OpenEBS for blue‑green and one‑click rollbacks, secrets move into HashiCorp Vault with sidecars and AppRole, pipelines run parallel stages and scheduled production jobs, and controlled chaos tests validate resilience.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:42What is Continuous Deployment
- 5:02Why Continuous Deployment
- 7:18Instrumentation
- 11:03Git strategy
- 13:21Stateful Sets
- 14:31Secrets
- 18:28Pipelines Stages
related talks
47mContinuous Delivery Meets OpenShift
40mContinuous delivery @ Axians with gitlab and openshift
57mA continuous fairytale
34mEnabling a Continuous Deployment Mindset
26mHuman Trust in Continuos Deployment
39mContinuous Deployment with Ansible
43mTo make mistakes is human. To auto-deploy it is DevOps.
22mOpenShift, or Kubernetes on steroids