@kelseyhightower This discussion is 🙄. K8s services operate on ~3 levels. Direct to pods via endpoints API, simple LB via Service IP (discovered via k8s API) and DNS to service IP. DNS as a bridge to workloads that aren't built for k8s.
We did all of this *because* DNS is so fraught.
@kelseyhightower But Twitter is such a shit show every time I see a "hot take" from a blue check I assume they are just engagement farming.
Either that or Ahmed is just uninformed.
@kelseyhightower One more comment. IMO there is need for a modern discovery API that is disjoint from any impl (k8s, consul, svc mesh). It is a necessary part of building secure systems (ex: use in conjunction with @SPIFFEio).
(I may do some of these! I'm writing this down in part to keep myself honest.)
Thought leading: Confidence is key. You can never admit that you are wrong. Win arguments by outlasting and exhausting the other party.
Thought leading: speak in universals. Single sentence sound bites that seem to express universal truths are true thought leadership. Admit no ambiguity.
One of the interesting things about AWS Firecracker is that it is (one of?) the first OSS projects *originated* by AWS. It will be interesting to see how outside contributions and community are curated. Some comments after a 2 minute look at the repo/docs:
First, there is a Code of Conduct (github.com/firecracker-mi…). It is very corporate though where violations are reported to an amazon alias. If a real community forms it'll be interesting to see if this shifts to be a community driven thing.
This coming week is a bit of a stay-cation as I hang out at home with the boy (9yo). I'm going to try not to get too sucked into work (but it is unavoidable). He wants to build a game in C++ together. We've decided to use SDL2 as the graphics library.
I'm watching some tutorials on building a basic game engine. All I can say is that C++ has changed quite a bit from when I last used it seriously. That includes my time at Microsoft and Google (building GCE).
Some of the new stuff looks really nice but there is a lot of it! And it isn't clear if I should target C++11 or C++14 or C++17. He insists on using mingw (I have no idea why) while I'm going with Visual Studio. We might want to use Xcode at some point too.
The US midterm elections are coming up and I want to support (with significant $) non-republican federal or gubernatorial candidates that have a chance of flipping the seat or are in chance of losing it. Do folks have resources for where my money can be most effective?
I'm not interested in (a) people telling me not to talk politics or (b) people telling me that my political leanings are wrong.
Thank you everyone for great suggestions and resources to look into. I now need to find time to sit down and build a spreadsheet. Keep the suggestions coming.
I wouldn't say that #Knative is overly complex. I'd say that it is early. Even the team says that it is only a 0.1 version. There is a lot to like there. Let me use all the nuance of Twitter to try and put some color on it.
First, the install story is more complex than it should be. YAML files with thousands of lines is huge. Much of that is HTML and such for dashboards. We need to find a better way. This also applies to Istio -- the install has config maps with quoted yaml that has quoted yaml.
Taking a hard dependency on Istio brings a lot of value but adds a lot to the complexity of the system. Installing Istio is complex especially depending on things like mutable admission controllers and auto sidecar injection.
Super interesting response to my thread yesterday from @jmoiron (h/t @copyconstruct). Thank you! There is a lot to digest there and I don't want to do that thing where I deconstruct it point by point so I'll try to hit some of the high points. jmoiron.net/blog/is-k8s-to…
First off: Jason is frustrated and his experiences are valid! This stuff isn't where we need it to be and there are undoubtably things that won't pan out over the long term. We are still early in this game and it is chaotic and exciting and confusing. I share that frustration.
Next wrt marketing: we are at the height of the hype cycle for Kubernetes. There nuggets of goodness can get lost in the effort to thought leader in more and more grand themes. Marketing gets out of control. This really bugs me and makes me grumpy.