As much as we would like all environments to be the same: they're not. In the end, each type of environment has a specific purpose and so has to vary compared to others.
A common sore point is managing databases: To save money, in dev the database should be run in-cluster, in staging it should be pre-filled with test data and in production you want to point to your beefy managed instance.
Handling these differences in Helm Charts or as directories in git gets old very quickly. Soon you will be making commits to get to the code to work in staging or production!
By separating environment specific configuration from environment agnostic configuration, you can start to make sense of this mess.
In this workshop, Humanitec’s CTO Chris Stephenson will show how teams can use Humanitec to run very different infrastructure in dev, staging and production while making it all feel the same.
He will show:
- How to think about the interfaces between systems
- How to create resource definitions that differ across environments,
- How, despite different infrastructure, promoting between environments is straightforward.
After a 30 minutes demo, there will be 15 minutes for Q&A. We’d like to encourage you to submit your questions in advance.
A recording of the workshop and related materials will be shared with all attendees afterwards.
Audience - who should join?
DevOps Engineers, Site Reliability Engineers, System Engineers, Infrastructure Kubernetes Administrators, Technical Architects, Application Developers with an affinity with DevOps and Technical Management.