Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Canonical introduces high-availability Micro-Kubernetes

zdnet.com

Post reply on HN
Print view View original

81–90 of 118 posts

Re: Canonical introduces high-availability Micro-Kubernetes

#81

Post by pjmlp »

zemo wrote: post #13

writing one application was hard so instead let's assume writing lots of tiny applications will be easier (???) but isolating them is hard so let's put them in containers but running containers is complicated so we need orchestration managers like kubernetes or something but running those things is too hard for someone whose job isn't to run kubernetes for a living so microk8s or minikube or k3s or whatever? that's t…

You are missing the business opportunities to do conference talks, write blog posts, best practices books, and sell consultancy services on how to sort out those problems.

That is why we are stuck in fashion industry nowadays.

Re: Canonical introduces high-availability Micro-Kubernetes

#82

Post by jakupovic »

nurgasemetey wrote: post #79
kavalg wrote: post #78

Earlier quoted context omitted.

Maybe not the answer you are looking for, but for small and not that critical workloads, I've so far been happy with docker swarm workloads on cheap cloud/VPS.

We run our platform in different cities and they are all on-prem(custom server or managed hypervisor). After hearing horror stories about kubernetes on prem, we are happy that we decided to go with docker swarm.

K8s is the new platform, you're just delaying the inevitable. Get with the program or suffer when your lack of knowledge makes you deficient in the platform uptake.

Re: Canonical introduces high-availability Micro-Kubernetes

#83

Post by enriquto »

bayindirh wrote: post #19
jrockway wrote: post #7

Earlier quoted context omitted.

To some extent, the distributed consensus is kind of the important part. If you have a bunch of components that don't know what state they're supposed to be in, you don't really have a cluster. Looking at the marketing documentation (I didn't read the code), they just wrote their own consensus and datastore instead of using etcd. So the underlying fundamental computer science problems still exist, but nobody has been…

> I just don't trust Canonical much... They lost me when I've tried their ubuntu server when I was lazy one day and greeted with their Landscape advertisement in the MOTD display. Then I installed armbian's ubuntu version because Debian version was not ready and found out that MOTD was downloaded from web every time I log in. Add analytics (now opt-in), forcing snaps and their silent-ish efforts to monopolize the lan…

Putting a single commercial, once, on the MOTD file is a sure way to tarnish the reputation of a whole distribution and its derivatives forever.

Re: Canonical introduces high-availability Micro-Kubernetes

#84

Post by akvadrako »

jakupovic wrote: post #82
nurgasemetey wrote: post #79

Earlier quoted context omitted.

We run our platform in different cities and they are all on-prem(custom server or managed hypervisor). After hearing horror stories about kubernetes on prem, we are happy that we decided to go with docker swarm.

K8s is the new platform, you're just delaying the inevitable. Get with the program or suffer when your lack of knowledge makes you deficient in the platform uptake.

However, being an early adopter is not usually wise. Better to wait until lots of other people have found the bugs and improved the documentation.

Re: Canonical introduces high-availability Micro-Kubernetes

#85

Post by thor24 »

koeng wrote: post #47
thor24 wrote: post #18

Earlier quoted context omitted.

> I use K3S for deploying an actual production cluster You mean when you want to run a small cluster of let's say less than 10 nodes (anything in single digits)? Why doesn't normal k8 work this way? like same tech but just less scale? (I should probably read more on the side myself as well, new to this K8 world).

Yep, it’s a small self hosted cluster on my own server hardware (VMs on Proxmox) I’m sure k8s would work, but k3s made it really easy for me to get going so now just has inertia.

I see, I assumed logically Kubernetes as a community would want to keep thing simple and keep it same across scale. For large scale there could be different variations (like switching storage backend) but for small/low scale tier keep it dead simple.

I am guessing there were valid reasons for the offshoots (k3s, microk8s etc.).

Re: Canonical introduces high-availability Micro-Kubernetes

#86

Post by emptysongglass »

tryauuum wrote: post #29
gravitas wrote: post #27

Earlier quoted context omitted.

I work in this space (being purposefully vague), you are getting a customized image of some sort - PXE really isn't related in this way, that's just a method to get the image onto the destination disk. The official Canonical Ubuntu Cloud Images produced for use this way have the MOTD behaviour and snapd in place based on my exposure to them. https://cloud-images.ubuntu.com/

we are using this thing — http://archive.ubuntu.com/ubuntu/ubuntu/dists/focal/main/ins... , it is loaded with PXE. It doesn't put a "customized image of some sort" on servers, it literally iterates through installer steps with the autoanswers provided by preseed file. You might say that it is customized since we wrote a preseed file. Well maybe, but it's not a "customized image". Also we didn't write any specific cod…

You may be in for a shock using Ubuntu Server 20.04 and later as it has switched to using cloud-init. Preseed files no longer work.

Re: Canonical introduces high-availability Micro-Kubernetes

#87

Post by thor24 »

moondev wrote: post #64
thor24 wrote: post #18

Earlier quoted context omitted.

> I use K3S for deploying an actual production cluster You mean when you want to run a small cluster of let's say less than 10 nodes (anything in single digits)? Why doesn't normal k8 work this way? like same tech but just less scale? (I should probably read more on the side myself as well, new to this K8 world).

It does. Upstream kubeadm - authentic kubernetes - can even run on a single node. Not sure why people choose k3s or microk8s when you can just as easily deploy the real thing.

That's exactly what i am confused about when only reading these things in isolation.

Re: Canonical introduces high-availability Micro-Kubernetes

#88

Post by emptysongglass »

nerdbaggy wrote: post #71

Would this be a good use case for docker swarm replacement? Right now I have about 100 containers on prem and need to find something to replace swarm

It's what we switched to from Swarm and it works great on anything larger than the equivalent of a t3.micro instance.

Re: Canonical introduces high-availability Micro-Kubernetes

#89

Post by gravitas »

emptysongglass wrote: post #86
tryauuum wrote: post #29

Earlier quoted context omitted.

we are using this thing — http://archive.ubuntu.com/ubuntu/ubuntu/dists/focal/main/ins... , it is loaded with PXE. It doesn't put a "customized image of some sort" on servers, it literally iterates through installer steps with the autoanswers provided by preseed file. You might say that it is customized since we wrote a preseed file. Well maybe, but it's not a "customized image". Also we didn't write any specific cod…

You may be in for a shock using Ubuntu Server 20.04 and later as it has switched to using cloud-init. Preseed files no longer work.

You should be able to use the "Legacy" (their new words) ISO installer. I'd be interested in your results if you get a chance to followup here. http://cdimage.ubuntu.com/ubuntu-legacy-server/releases/20.0...

Re: Canonical introduces high-availability Micro-Kubernetes

#90

Post by mroche »

krimeo wrote: post #56
oso2k wrote: post #53

Earlier quoted context omitted.

Haha. I still work for Red Hat, and Consulting at that. My pay is determined by how many billable hours I put in and my customer reviews. Not directly by how much you buy.

I thought there is no Red Hat anymore.

Red Hat is a subsidiary of IBM, not acquired and absorbed. It is very much its own thing within the company as a whole.
Post reply on HN