Kubernetes Is Your Private Cloud
oneuptime.com
Kubernetes Is Your Private Cloud
1–10 of 92 posts
Re: Kubernetes Is Your Private Cloud
#2Re: Kubernetes Is Your Private Cloud
#3IMO an article like this shouldn't just make the claim - it should show how to do it at the home lab level.
Re: Kubernetes Is Your Private Cloud
#4Except you own ops, management, extension, interoperability, access, security, scalability, redundancy… words cannot express how ridiculous all of the koober propaganda is
Re: Kubernetes Is Your Private Cloud
#5“Everything You Expect from a Cloud, Running on Your Terms“* Except you own ops, management, extension, interoperability, access, security, scalability, redundancy… words cannot express how ridiculous all of the koober propaganda is
Re: Kubernetes Is Your Private Cloud
#6Re: Kubernetes Is Your Private Cloud
#7“Everything You Expect from a Cloud, Running on Your Terms“* Except you own ops, management, extension, interoperability, access, security, scalability, redundancy… words cannot express how ridiculous all of the koober propaganda is
Re: Kubernetes Is Your Private Cloud
#8Re: Kubernetes Is Your Private Cloud
#9“Everything You Expect from a Cloud, Running on Your Terms“* Except you own ops, management, extension, interoperability, access, security, scalability, redundancy… words cannot express how ridiculous all of the koober propaganda is
Cloud’s big promise was speed to market and price, and let’s be honest, price is no longer there compared to a decent operation.
The one thing where clouds remain kings is speed for small teams. Any large enough company should probably Ask themselves whether running their own operation using ias would be a better choice.
Re: Kubernetes Is Your Private Cloud
#10- Upgrading a kubernetes cluster may as well be an olympic sport. its so draconian most best practice documentation insists you build a second cluster for AB deployment.
- load balancers come in half a dozen flavours, with the default options bolted at the hip to the cloud cartel. MetalLB is an option, but your admin doesnt understand subnets let alone BGP.
- It is infested with the cult of immutability. pod not working? destroy it. network traffic acting up? destroy the node. container not working? time to destroy it. cluster down? rebuilt the entire thing. At no point does the "devops practitioner" stop to consider why or how a thing of kubernetes has betrayed them. it is assumed you have a football field of fresh bare metal to reinitialize everything onto at a moments notice, failure modes be damned.
what your company likely needs is some implementation of libvirtd or proxmox. run your workloads on rootless podman or (god forbid) deploy to a single VM.