DevOps 016: Kubernetes as Infrastructure Abstraction with Oleg Chunikin
In this episode of Adventures in DevOps the panel interviews Oleg Chuninkin, CTO of Kublr. Oleg starts by explains what Kublr is all about and how he got the idea of using Kubernetes as an infrastructure abstraction. He and the Kublr team were trying to decide the most productive way to think of Kubernetes.
Oleg advocates for using Kubernetes locally and shares how you can then orchestrate your architecture so you can see what it will do in productions. Charles breaks down a few of the ideas Oleg shares. Oleg explains how the portability of Kubernetes can be used and shares recommendations with the panel on how to run a Kubernetes in a lightweight way.
The panel asks Oleg about the pressure for a cloud independent service and how these effects application requirements. Oleg shares some resources in answer. Moving on the panel considers Olegs comment about the layered architectural approach. Oleg outlines the layered architectural approach and explains what he means by layered. He explains the benefits of this approach.
- Scott Nixon
- Charles Max Wood
- Oleg Chunikin
"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!
Charles Max Wood:
- Host spots available! Contact me if you are interested.
- Talk with friends
What is Kublr?
Kublr is an enterprise-grade Kubernetes management platform.
Why use the layered architectural approach?
It provides an openness and makes sure you do not stand in the way of Kubernetes and what Kubernetes does best.
What challenges do developers face moving from one platform to another?
There are a lot but by keeping concerns and layers separate you make it possible to move it piece by piece.
What is the downside to using open source resources?
Support can be inconsistent compared to enterprise solutions.