Live data from Hacker News

Domesticating Kubernetes

blog.quickbird.uk

91–100 of 100 posts

Re: Domesticating Kubernetes

#91
post #82

Earlier quoted context omitted.

I'll bite. One thing I found in running my home lab was that I kept having to burn it to the ground & rebuild it regularly anyway. For example, dist-upgrade never really works: every time I try I just end up wasting a couple days wrestling with it and then giving up and rebuilding the machine from scratch. Even if I just assumed that I'd have to build from scratch every time, differing app and library versions meant…

I think you could achieve something similar but by just using simple standalone containers that you start with Podman or Docker. Once you have the OS up and running, then all you need to do is push the configuration to the server (I just rsync systemd service files) and start the services. Persistent data is stored elsewhere anyway, so moving a service is just a matter of copying a directory over to another machine a…

I could, but with the same effort to set that up, I could have a full k8s setup...it doesn't actually save me any time to do it the "simple" way.

Re: Domesticating Kubernetes

#92
post #86

Earlier quoted context omitted.

what are some usecases where you need systemd alongside docker containers?

systemd can restart your container if it crashes. It can also start it if you reboot your system.

can you set a restart policy with just Docker?

Re: Domesticating Kubernetes

#93

Earlier quoted context omitted.

No I have not. Going on 3 years now?

Great. So you do not have any experience with the worst-case scenario. That is exactly my point. I would like to hear your opinion once you fixed an outage that is caused by K8s.

Well what is this outage caused by?

Not understanding how k8s work, or actual provider screwing up?

if the former - I try to read carefully and test my workloads in a test cluster before I do it in prod.

if the latter, I think google has excellent operational excellence.

This is like saying you wouldn't take driving advice from me until I total a few cars. Perhaps I didn't total a few cars because I make good driving decisions?

Re: Domesticating Kubernetes

#94

Earlier quoted context omitted.

Great. So you do not have any experience with the worst-case scenario. That is exactly my point. I would like to hear your opinion once you fixed an outage that is caused by K8s.

Well what is this outage caused by? Not understanding how k8s work, or actual provider screwing up? if the former - I try to read carefully and test my workloads in a test cluster before I do it in prod. if the latter, I think google has excellent operational excellence. This is like saying you wouldn't take driving advice from me until I total a few cars. Perhaps I didn't total a few cars because I make good driving…

An outage that is caused by k8s. You can pick a random from this list. https://github.com/hjacobs/kubernetes-failure-stories

>>This is like saying you wouldn't take driving advice from me until I total a few cars

No, I am saying you do not have enough experience with k8s. That is all. Totaling a car implying you are driving, using k8s implying that whoever wrote that particular part of k8s is driving. You have some control but ultimately you need to understand what is going on. As that list shows many companies who put k8s into production learned it in a hard way.

Re: Domesticating Kubernetes

#95

Earlier quoted context omitted.

Well what is this outage caused by? Not understanding how k8s work, or actual provider screwing up? if the former - I try to read carefully and test my workloads in a test cluster before I do it in prod. if the latter, I think google has excellent operational excellence. This is like saying you wouldn't take driving advice from me until I total a few cars. Perhaps I didn't total a few cars because I make good driving…

An outage that is caused by k8s. You can pick a random from this list. https://github.com/hjacobs/kubernetes-failure-stories >>This is like saying you wouldn't take driving advice from me until I total a few cars No, I am saying you do not have enough experience with k8s. That is all. Totaling a car implying you are driving, using k8s implying that whoever wrote that particular part of k8s is driving. You have some c…

Sorry I’m not following

Should I compile a list of failure stores for companies that ran Linux because Linux is complicated or has had various bugs?

How about a list of failure stories of how Ruby causes problems?

You can get errors with any system. You would need to prove to me that k8s has say more errors per day than a competitor (lambda? VMs). I just don’t understand...

Re: Domesticating Kubernetes

#96

Earlier quoted context omitted.

An outage that is caused by k8s. You can pick a random from this list. https://github.com/hjacobs/kubernetes-failure-stories >>This is like saying you wouldn't take driving advice from me until I total a few cars No, I am saying you do not have enough experience with k8s. That is all. Totaling a car implying you are driving, using k8s implying that whoever wrote that particular part of k8s is driving. You have some c…

Sorry I’m not following Should I compile a list of failure stores for companies that ran Linux because Linux is complicated or has had various bugs? How about a list of failure stories of how Ruby causes problems? You can get errors with any system. You would need to prove to me that k8s has say more errors per day than a competitor (lambda? VMs). I just don’t understand...

>> Hosted k8s has changed my life. Let me focus on my business and not my infra.

This is the claim that you made. I would argue that since you do not have experience with it you perceive it as you do not need to focus on your infra. Once you run into a failure with k8s and you actually need to fix it, this might change. That is all.

Re: Domesticating Kubernetes

#97

Earlier quoted context omitted.

Sorry I’m not following Should I compile a list of failure stores for companies that ran Linux because Linux is complicated or has had various bugs? How about a list of failure stories of how Ruby causes problems? You can get errors with any system. You would need to prove to me that k8s has say more errors per day than a competitor (lambda? VMs). I just don’t understand...

>> Hosted k8s has changed my life. Let me focus on my business and not my infra. This is the claim that you made. I would argue that since you do not have experience with it you perceive it as you do not need to focus on your infra. Once you run into a failure with k8s and you actually need to fix it, this might change. That is all.

Why would it

I have run into Linux failures. I still use Linux.

I have ran into bugs in Java. I still use Java when it makes sense.

So not sure what you are trying to get to. You give up on a technology the first time you have a problem?

Re: Domesticating Kubernetes

#98
post #86

Earlier quoted context omitted.

systemd can restart your container if it crashes. It can also start it if you reboot your system.

can you set a restart policy with just Docker?

I don't know. But if you can, that still leaves you the second use case: starting your container on reboot.

Can you have Docker do that too?

Re: Domesticating Kubernetes

#99
post #70
post #65

Earlier quoted context omitted.

The pi 4 has gigabit ethernet. I'm not sure why you'd think it has "woeful network performance". The 3B+ could only do a couple hundred megabit, which was somewhat mediocre, though.

If they've fixed it with the 4 then that's great, ISTR in previous versions the Ethernet was backed by the shared USB controller ( https://raspberrypi.stackexchange.com/questions/45130/why-do... ), hence my question.

The shared USB controller wasn't the issue, the lack of USB 3 was.

Re: Domesticating Kubernetes

#100
post #99
post #70

Earlier quoted context omitted.

If they've fixed it with the 4 then that's great, ISTR in previous versions the Ethernet was backed by the shared USB controller ( https://raspberrypi.stackexchange.com/questions/45130/why-do... ), hence my question.

The shared USB controller wasn't the issue, the lack of USB 3 was.

OK, "the use of a backing bus that wasn't fast enough".
Post reply on HN