Live data from Hacker News

Kubernetes 1.18

kubernetes.io

31–40 of 132 posts

Re: Kubernetes 1.18

#31
post #23
post #18

Earlier quoted context omitted.

Nomad and Consul from Hashicorp.

which is way more complex to setup than k3s

Perhaps installation and config are not as streamlined as one of the many available k8s setup tools, but the tools themselves are much easier to understand and less broad than the k8s system.

Used nomad/consul/fabio at a previous job for running containers, it was very easy to adopt. Way less new concepts as well.

It's worth mentioning I later chose GCP managed kubernetes for a small cluster to run at my startup. I had to learn a few new things, but I'm not familiar of any "nomad as a service" offerings, so I went with k8s on Google cloud.

Re: Kubernetes 1.18

#33
post #6

Earlier quoted context omitted.

What are recommendable simpler system examples, or managed options you allude to?

Google Cloud Run, AWS Fargate, Google App Engine, Heroku etc. are comparable experiences to Kubernetes if you have the flexibility of (1) running on cloud (2) not having to configure host OS or rely on host GPUs etc. Disclaimer: I work at Google Cloud Run.

This comment makes no sense.

There is AWS Fargate for Kubernetes, AWS Elastic Kubernetes Service, DigitalOcean Kubernetes, Google Kubernetes Engine etc.

All of which are on the cloud and all of which don't require you to configure host OS etc. Some offer full control over node configuration e.g. EKS whilst others manage that for you e.g. Fargate.

Re: Kubernetes 1.18

#34

Anyone have a recommended guide for Kubernetes?

The KubeAcademy courses are nice little (free, no-reg) intros, and they have transcripts if you read faster than you watch: https://kube.academy/courses

Thanks for the link. The presentation looks very nice, I'm going to give the course a try, especially since it's free (I've been considering a subscription to either Linux Academy or A Cloud Guru).

EDIT: Upon further investigation, I see that there's not much technical content provided here. So it goes. Thanks anyways.

Re: Kubernetes 1.18

#36
post #6

Earlier quoted context omitted.

Google Cloud Run, AWS Fargate, Google App Engine, Heroku etc. are comparable experiences to Kubernetes if you have the flexibility of (1) running on cloud (2) not having to configure host OS or rely on host GPUs etc. Disclaimer: I work at Google Cloud Run.

This comment makes no sense. There is AWS Fargate for Kubernetes, AWS Elastic Kubernetes Service, DigitalOcean Kubernetes, Google Kubernetes Engine etc. All of which are on the cloud and all of which don't require you to configure host OS etc. Some offer full control over node configuration e.g. EKS whilst others manage that for you e.g. Fargate.

Thanks for repeating what I already said. I responded to the question asked. OP asked if there are simpler alternatives. These are simpler alternatives to Kubernetes.

I don't know which part you're not getting, but it appears that this person's intention is not to learn Kubernetes or deal with nodes in the first place.

Re: Kubernetes 1.18

#37
post #11

Earlier quoted context omitted.

When I think about k8s complexity, I can only understand this argument if I'm the one dealing with the infrastructure required. If I have to install k8s in my servers, then I'll probably need to think hard about security, certificates, hardware failures, monitoring, alerting, etc. It's a lot of work. However, if I use a managed k8s service, I probably don't have to think about any of that. I can focus on the metrics…

Honestly getting a cluster running is the easiest part. It’s all the add one like istio that make it complicated.

You don't need Istio if your application is simple. I think Istio makes more sense when your application makes heavy use of peer-to-peer pod connections. If you can get away with a simple queue as a bus, it should remain simple. I think!

Re: Kubernetes 1.18

#38
post #5

Reminder to everyone that unless you have a truly massive or complex system, you probably don’t need to run K8s, and will save yourself a ton of headaches avoiding it in favor of a more simple system or using a managed option.

People say this every time anything related to k8s gets posted and I always wonder who it’s addressed to. The system doesn’t actually have to be that complex for kubernetes to be useful and kubernetes isn’t that hard to run. We’re in the process of switching from ecs to kubernetes and while it’s not an easy thing to make ready for production, it enables so much that wouldn’t even be possible with ecs. To me this advi…

What does it enable compared to ECS?
Post reply on HN