Habitat Automation that travels with the app
summary
Habitat packages a Spring Boot service inside a reproducible studio, builds a JAR and produces a signed artifact pushed to a public Depot, then promotes from unstable to stable channel and exports images for Docker or Kubernetes. A resident supervisor runs a gossip ring so supervisor gossip ring propagates config and performs rolling updates; demo shows three instances receiving new configuration and an updated package. Production adoption takes days—one team deploys Habitat in under a week and integrates with Jenkins.
AI-written summary · about
chapters (8)
- 0:00habitat APPLICATION THAT TRAVELS WITH THE APP
- 5:25HOW IT DOES THAT Encapsulates and automates your application Package Management
- 9:57SUPERVISOR Supervises your service(s) Can manage service configuration Can update the service package
- 12:07CONSTRUCT AUTOMATION WORKFLOWS
- 12:21CONTINUOUS DELIVERY Builder Reverse Deps Rebuilds
- 13:12CONTINUOUS DEPLOYMENT Depot Channels Supervisors channel subscription
- 25:56WHAT WE DID WITH HABITAT 1 week Jenkins integration Centralized configuration Future proof for Infrastructure
- 26:40Incremental deployment Common packaging for every apps Common config management interface Technical interface between devand ops
related talks
39mSimplifying Container Operations with Habitat
45mGetting Started with Habitat
39mAchieving Cloud Agnostic Application Deployment with Habitat
40mHabitat in Production
37mHabitat Essentials - An Absolute Beginner's Guide
45mThe Evolution Of Automation
31mHabitat Builder: Cloud Native Application Automation - Elliott Davis & Fletcher Nichol, Chef.io
44mKubernetes & Habitat