Kubernetes 1.16
kubernetes.io
Kubernetes 1.16
1–10 of 80 posts
Re: Kubernetes 1.16
#2that owl looks pissed
Re: Kubernetes 1.16
#3that owl looks pissed
angry bird for sure
Re: Kubernetes 1.16
#4I 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 ... then later:
"""A declarative API allows you to declare or specify the desired state of your resource and tries to keep the current state of Kubernetes objects in sync with the desired state."""
But wait, I thought the resource _was_ an API endpoint? The API allows me to declare the desired state of my API?
I know K8s is not Borg and I know a lot of xooglers hate Borg but at least the Borg documentation was concise and made sense.
Re: Kubernetes 1.16
#5Can it be installed, yet?
Re: Kubernetes 1.16
#6I 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 ...…
I think this will be a due to multiple authors and the curse of the expert.
Kubernetes is fairly gigantic now and continuing to spurt out in all sorts of directions, feature-wise.
"The full-time job of keeping up with Kubernetes"[0] was published in February 2018 and nothing's slowed down.
[0] https://gravitational.com/blog/kubernetes-release-cycle/# (and the HN discussion at the time: https://news.ycombinator.com/item?id=16285192)
Re: Kubernetes 1.16
#7I 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 ...…
Both of your examples made sense to me, but when you take a step back that sentence doesn't really mean anything without context.
A "resource" === "endpoint" in the sense that the endpoint defines where you can define the configuration of a specific resource. They are being specifically vague I am assuming because of the concept of CRDs.
But without that sort of knowledge ("Hey, Kubernetes has a customizable API using custom resources!"), that sentence is rather hard to unpack.
edit: Thinking about it some more I suppose an endpoint is an overloaded term w.r.t. Pod IPs.
Re: Kubernetes 1.16
#8I 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 ...…
CRD is Custom Resource Definition
Re: Kubernetes 1.16
#9I 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 ...…
Both of your examples made sense to me, but when you take a step back that sentence doesn't really mean anything without context. A "resource" === "endpoint" in the sense that the endpoint defines where you can define the configuration of a specific resource. They are being specifically vague I am assuming because of the concept of CRDs. But without that sort of knowledge ("Hey, Kubernetes has a customizable API usin…
When you submit a CRD to Kubernetes you get a few things:
1. The CustomResourceDefinition itself, a document that tells Kubernetes "Hey, I have a kind of custom resource I want you to know about".
2. Instances of that custom resource that have been submitted to Kubernetes. "Submitted how?", you ask, which leads to:
3. When you submitted the CRD, Kubernetes automatically created HTTPS endpoints based on the values of the group, kind and version of the CRD. It accepts that custom resource at that endpoint.
What makes dealing with CRDs confusing, in my experience, is that "CRD" is used in two senses. One is the actual resource, the actual chunk of YAML submitted to Kubernetes that contains "kind: CustomResourceDefinition".
The second sense is to bundle together all the things that can be done with or flow from CRDs. Usually this is where you hear about controllers, operators and so on, but it will still be called "the Foo CRD", even though that's like referring to a 3-tier application as "the Foo table schema".
Re: Kubernetes 1.16
#10We're moving away from Kubernetes because managing even a simple implementation is a full-time job. Obviously Kubernetes is meant for enterprises, but I've seen seed round/series A startups with a small engineering team using it.
We were at a crossroad. Either we hire an SRE that has extensive kubernetes experience for $130K/year or we move to a managed platform until we actually need those capabilities.
We're happy with the move and the pressure relief is tremendous. Now we can focus on features and not whether or not deploying is using ENV vars from our local machines and causing the system to crash.