HomeAboutMailing ListList Chatter /0/0 3.230.142.168

kubernetes anyone?

2022-05-04 by: Ed King
From: Ed King 
------------------------------------------------------
so while I'm on, ahem, vacation, I'm taking the time to study some stuff
that I've been wanting to study...    kubernetes being one of them

Been watching youtube tutorials, and I'm at the point in the tutorial where
I set up a kubemini lab

I was just wondering...   is anyone on chugalug actually using this stuff
in PRODUCTION, or is it just hype?

=============================================================== From: Dan Danese ------------------------------------------------------ My company has some products that use kubernetes. Machine learning and ai st= uff.=20 Sent from my iPhone rote: hat I've been wanting to study... kubernetes being one of them e I set up a kubemini lab n PRODUCTION, or is it just hype?

=============================================================== From: Tia Lobo ------------------------------------------------------ My company has customers using k8s in PRODUCTION. But k8s is about where "the cloud" was 10+ years ago (both the tech and adoption). My company, Netapp, makes tools for managing storage for applications running in K8s. This is the one I work on: https://cloud.netapp.com/astra Our customers, who I am not at liberty to name but several Fortune 50 companies are on the list, do use k8s in PRODUCTION. Personally, I am always surprised this stuff works at all. It seems like a bajillion loosely coupled applications, most of which are not stateful and k8s is constantly spinning new containers to provide HA. On the other hand, containers provide Just Enough Abstraction(c), to allow the physical layer to be "whatever". So our tools work on Azure, GCP, AWS and private. I think this is the first level of abstraction that allows applications to be written once and run on all the public clouds (and private). I suspect we'll see more of it. But I don't see any companies porting all of their applications to this stack. It's usually greenfield projects that are being spun up on timelines that just aren't practical for more "traditional" stacks (like VMs or physical hardware). That is, except for the companies, like mine, that are doubling-down on this tech. -Erica -=--=---=----=----=---=--=-=--=---=----=---=--=-=- Erica Wolf (she/her) On Wed, May 4, 2022 at 12:25 PM Ed King wrote:

=============================================================== From: Mark Huguet ------------------------------------------------------ I've been working with Kubernetes for about 4 years now, and as a Kubnernetes/DevSecOps SME for the last 2 years. There are 3 places that are huge value adds (and are worth keeping in mind as you learn). 1) Developers love being able to define the container and send it your way without having to plan for the system it's being deployed on (once they understand how containers work). 2) Fault tolerance and self healing orchestration sound like black magic to most IT managers, I have demonstrated forced failures without downtime only to have managers question the validity of the demo (but once they wrap their head around it, they love it) 3)Lack of scalability is the most common failure mode of failed cloud migration strategies. Per CPU cycle, the cloud is almost always more expensive than on prem. Cost savings come from the ability to only pay Per CPU cycle consumed. Kubernetes built-in scalability makes cost saving in the cloud seamless (for properly architected workloads). Now for the bad news, there are very few opportunities for administering Kubernetes without having to do development work. At bare minimum most organizations will want Infrastructure as Code, but realistically someone needs to teach the developers how to code, build and package for Kubernetes. Often that expectation falls on the person with the most knowledge of the tech whether they are a dev or not. Therefore coaching devs has been a significant component of my Kubernetes work.

=============================================================== From: "Mike (meuon) Harrison" ------------------------------------------------------ I've played with K8s and other container systems. My personal opinion is at small scale, it's better to write code and build systems that work well without it. At large scale: It's awesome and incredible and you build entire ecosystems to use it well with serious people that know what they are doing from both the DevOps and programming perspective. You'd make a great one of them people.

=============================================================== From: Lisa Harrison Ridley ------------------------------------------------------ It is not hype, we run our entire client hosting on managed K8s on Google Cl= oud. We have roughly 100 or so clients with dev, staging and production sit= es, all managed with horizontal scaling on K8s. Sent from my iPhone e: in t small scale, it's better to write code and build systems that work well wi= thout it. s to use it well with serious people that know what they are doing from both= the DevOps and programming perspective.