Cultivating Containers: Best Practices for Gen 3 Cloud Management


Last night, the ElasticKube team sponsored a San Francisco Cloud Mafia meetup with AppOrbit. While containers have been around for a while, the varied topics and questions reflect the fact that most companies are in the early stages of using containers. Topics ranged from best practices for container management at scale, to namespaces, to picking a repo.

After some yummy mediterranean and mexican food (“mediterran-ican”), CTO and co-founder of ElasticBox, Alberto Maestro, kicked off the evening with a review of the generational shifts in cloud management platforms, highlighting Generation 1 as being workflow driven with an emphasis on flexibility over reusability. Generation 2 is defined as model-driven or declarative with a premium placed on reusability over flexibility. Finally, he described Generation 3 as container driven with configuration management being done at build time, not deploy time. Gen 3 is typified by a single abstract container infrastructure model. Modern companies are moving towards Gen 3 cloud management.

With this context, Alberto then explained why we selected Kubernetes over other solutions in the market as the platform for our container management solution.

Why Kubernetes?

He then shared ElasticKube, an open source project for container management on top of Kubernetes. His demo included authorizing new users, managing a template catalog of charts from your repo and understanding the resources used for containers and pods. Finally, he covered the learning from the team’s experience with containers and Kubernetes and offered the following advice:

1. Containers behave differently per environment
2. Invest in a fast repo
3. Understand the network model of your container management system
4. Log everything

Check out the full presentation here:

We’re excited to be part of the broader Kubernetes community and look forward to your feedback.

Categories: Uncategorized