Automate Everything
summary
Builds run on CircleCI, npm packages get semantic version bumps and automated changelogs via conventional changelog, Docker images are built and pushed to Google container engine registry, and Kubernetes serves containers. A reusable deployment repository holds bash scripts called from CI; a surprising cluster constraint appears — Kubernetes rolling updates act as a rolling update singleton so CI must enqueue deployments — so a queue consumer and manual-trigger dashboards, Slack notifications and SSH-protected sites are implemented and tested.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:00Requirement
- 4:02Build Docker Containers
- 6:26Creating a Deployment Repository
- 6:53Create a Deployment Repository
- 7:29Pitfalls
related talks
01h 03mYet Another Continuous Delivery Talk
25mIncrease App Confidence Using CI/CD and Infrastructure as Code
39mKubernetes-centric CI/CD
47mGitLab CI and Kubernetes: deploying Applications continuously to Kubernetes
46mA Security State of Mind: Continuous Security with Kubernetes
24mIncrease App Confidence Using CI/CD & Infrastructure as Code
37mDesigning Cloud Ready Applications
06mBuilding Continuous Delivery Pipelines