smarterclayton

15 ms·

31.
by smarterclayton 4y ago
At the time we designed the StatefulSet, the resize behavior hadn’t been designed / finalized. Now that it has, it’s really a matter of someone having the time and patience to drive it though. I don’t know whether someone has sorted ou
32.
by smarterclayton 5y ago
Kubernetes supports both JSON patch and merge patch, and it has been a continuous source of amazement to me (in the “that’s a bloody giant hole in the ground” sense) of how hard actually calculating, representing, and developing durable int
33.
by smarterclayton 5y ago
One of the stories I provided for the documentary that didn’t make it (but is one of my favorites) relates to an early 2015 discussion I had with Brian Grant (googler / architect / worked on Omega / also in the documentary).
34.
by smarterclayton 5y ago
When Gateway API lands we definitely plan to streamline everyone moving to that (since it’s the superset of Routes and Ingress and supports the features we didn’t want to lose going back to ingress). That should help. We have considered ha
35.
by smarterclayton 5y ago
For context, the reason Routes were designed to inline cert info (about 6-12mo before ingress) was that ingress controllers (which run on nodes) having the ability to read all secrets (which means the ingress controller has to be considered
36.
by smarterclayton 5y ago
If you use the reflection package in Go, the dead code elimination optimization step does not run if you use reflect.Method to look up a method because you can use reflect to reach those methods and the linker preserves the possibility. Unf
37.
by smarterclayton 5y ago
Depending on the container runtime in use (containerd, crio), a separate process is managing and running those container processes (so k3s is telling that process what to do, but doesn’t “own” the containers). Also, modern container runtim
38.
by smarterclayton 5y ago
The Lego Star Destroyer has several “hammer of Thor” greebles (the interesting decorative surface details) in the engine section
39.
by smarterclayton 5y ago
Is there a supporting citation for the 85% number? I looked at https://en.m.wikipedia.org/wiki/Jewish_Bolshevism and this seems to be a specific factual inaccuracy (since that number seems hard to believe on the surfac
40.
by smarterclayton 5y ago
Right now it’s mostly the CRI/kubelet interaction (which polls the container runtime for containers) and metrics scraping generating the garbage. Having an incremental CRI watch (vs poll) has been on the backlog for years, but correctn
41.
by smarterclayton 5y ago
Most (but not all) overlay networks are implemented in kernel. If you compromise one node in a cluster, you can fairly trivially snoop traffic, bias other nodes to send traffic through you, or listen via various mechanisms such that you ca
42.
by smarterclayton 5y ago
And making it so that "many clusters" look exactly like "one cluster" is one of the goals the kcp prototype was exploring (although still early) because I hear this ALL the time: 1. 1 cluster was awesome 2. Many clusters
43.
by smarterclayton 5y ago
Other than bugs around bad connections causing hangs (the kubelet is less vulnerable to pathological failures in networking causing it to stall), nothing significant. Kube is designed for nodes to have continuous connectivity to the control
44.
by smarterclayton 5y ago
Wow, I’d forgotten about this. The reason no one has fixed it is partially because I didn’t do a great job of describing what the fix was I expected to see (clarified now). Reopened and will poke folks to look.
45.
by smarterclayton 5y ago
I’m pretty sure the author just wasn’t as familiar with the topic as they should have been. Should have been caught during editing though. As Joe notes, this was just how you most easily encode binary data in JSON. We did discuss that the
46.
by smarterclayton 5y ago
It’s not a requirement at Red Hat, because anyone can be converted to the open source religion. This surprised me when I started - I thought I would need to be indoctrinated, but then it just became normal to see open source as the only wa
47.
by smarterclayton 6y ago
I worked with tech companies and some banks in the early days of Kubernetes who were deep in Mesos and many of them felt the same way. It’s really hard to see this as it’s happening. Kubernetes is absolutely “worse is better” when it comes
48.
by smarterclayton 6y ago
As an early participant, while someone might have had this plan, I certainly did not hear this ever stated by anyone. Having the ability to run on Mesos was discussed as interesting and in the spirit of community but the work we did trea
49.
by smarterclayton 6y ago
That’s not true, because I’m the original author of ObjectMeta and I did it in golang. :) Half of the point of Kube is that every object looks similar enough that you can deal with them generically. ObjectMeta is what enforces that, so yes
50.
by smarterclayton 6y ago
We (Red Hat) sat down with the Mesosphere team pre-Kubernetes and were seriously considering Mesos and Mesosphere to replatform OpenShift (our PaaS) onto. When Google decided to make a run at Kubernetes, we decided to switch, despite having
51.
by smarterclayton 6y ago
Yes, separate legal entity, combined financial entity (although I know little about the financial details).
52.
by smarterclayton 6y ago
We talked about it recently, and certainly people want to do this, but I don’t see it happening anytime soon in core. Downstreams are free to carry patches though and many do. It’s more that the core team doesn’t have the time to support t
53.
by smarterclayton 6y ago
If you run etcd as a singleton you already get this behavior - consensus is shortcircuited and you only have to pay the cost to write to durable storage (which is already heavily batched). And you need durable writes so you can crash recov
54.
by smarterclayton 6y ago
Wow, I’d didn’t realize the 4.1 docs didn’t get updated - newer doc versions are correct in that disconnected subscriptions just manually entered via OCM. 4.1 didn’t include the support for disconnected clusters and at the time the docs we
55.
by smarterclayton 6y ago
As the person who has worked on making sure telemetry is useful and valuable for users and customers (helping drive insight into quality of kube and close the loop on fixing persistent issues), can you provide some more details about how we
56.
by smarterclayton 6y ago
All of the patterns and default code referenced there were things I wrote or helped write or reviewed, and while a certain “java patterns” mindset was common in early devs, I can assure you we didn’t transcribe it from Java, we simply used
57.
by smarterclayton 6y ago
Yes, to run tests that root your whole cluster, the test running for conformance grants “root your cluster” permissions. I occasionally regret the defaults we picked because people get frustrated that random software off the internet doesn’
58.
by smarterclayton 6y ago
A concrete example here is that almost everything in the Kubernetes ecosystem (the control plane, operators, integrations, etc) is CPU bound by time spent Marshalling/Unmarshalling JSON or protobuf. So in some domains it’s all that mo
59.
by smarterclayton 6y ago
Of course, to be able to see the signal, you have to be ruthless to noise. Deflake first, disable if you must, but never stop until it goes green and then be ruthless about keeping it that way.
60.
by smarterclayton 6y ago
There’s one particular domain where this question runs deep - tests that verify parts of distributed systems. Note: please do not extrapolate any problem described below outside of distributed systems. For instance in Kubernetes we run lots

More ›