Live data from Hacker News

Kubernetes 1.16

kubernetes.io

31–40 of 80 posts

Re: Kubernetes 1.16

#31
post #4

I wish their tech writers would give us more English and less jargon. I pondered these release notes and the documentation earlier today and I still can't puzzle out why "custom resource" is initialized as "CRD". And the rest of this gibberish is just meaningless. """A resource is an endpoint in the Kubernetes API that stores a collection of API objects of a certain kind.""" OK, almost completely free of meaning ...…

It's a OSS project, so if there is feedback filing an issue on the docs or submitting a PR is hugely beneficial. The docs team has a single full-time technical writer and the rest is contributions from the community.

Re: Kubernetes 1.16

#35
post #30

Earlier quoted context omitted.

Why not just used managed Kubernetes? Every cloud vendor has it, even Tier 2 operators like DigitalOcean. Running Kubernetes is vastly different for using it to run your apps. You really shouldn’t do the former unless you have to be on-Prem or have some other need.

What makes DO tier2? I use 1 linode for personal stuff, but otherwise, I'm all in on dedicated baremetal. From my perspective, DO is just another cloud vendor.

I'd say because they have way less products and glue services between these than the big ones (GCP, AWS, Azure).

Just compare the list on the product pages:

- https://www.digitalocean.com/products/

- https://aws.amazon.com/products/

Also DO doesn't have a lot of more niche services like Redshift, Mail, ML

Re: Kubernetes 1.16

#36
post #30

Earlier quoted context omitted.

Why not just used managed Kubernetes? Every cloud vendor has it, even Tier 2 operators like DigitalOcean. Running Kubernetes is vastly different for using it to run your apps. You really shouldn’t do the former unless you have to be on-Prem or have some other need.

What makes DO tier2? I use 1 linode for personal stuff, but otherwise, I'm all in on dedicated baremetal. From my perspective, DO is just another cloud vendor.

AWS, GCP, and Azure have a huge portfolio of datacenters, infrastructure, compute, networking, storage, security, databases, analytics, AI/ML, and other managed services that are completely missing from DigitalOcean.

DO is tier 2 because it provides basic IaaS components along with S3/Spaces, managed databases, load balancing, and K8S as compared to providers like Linode which would be tier 3 and below.

Re: Kubernetes 1.16

#37
post #34

So, do we expect Kubernetes to ever replace Borg?

That sounds like a technical question that was given a political answer. ("Kubernetes is so great we don't want to keep it all to ourselves here at Google, let's give it to an open source foundation!")

Re: Kubernetes 1.16

#38

A question on endpoint slices:why dont they send patch updates? A patch is the delta that changes an object instance.

Because safe generalized PATCH operations require the client and server to agree on the immediately prior state and the order of application of patches to avoid creating “Frankenstates”. They’re not a good general purpose API building block.

Re: Kubernetes 1.16

#39

Earlier quoted context omitted.

I don't understand. You had a problem; you needed to run a distributed system with containers which Kubernetes is perfect for. Did your problem disappeared or did your requirement changed or did you change to a different container orchestrator tool?

I'm saying we didn't have a problem that Kubernetes solved. A lot of seed-round/Series A startups also are quite simple, but hopping onto Kubernetes because it's "enterprise".

Really disappointed in the people downvoting you for sharing your personal experiences.

Re: Kubernetes 1.16

#40
post #34

So, do we expect Kubernetes to ever replace Borg?

Assuming that Borg it's proprietary (IE, zero documentation, no community, no real user cases outside of Google), yes. As all Google projects, let's wait its complexity doesn't collapse under its own weight, leaving no options but to move to somewhere simpler, which isn't on the horizon.
Post reply on HN