Profile avatar
munnerz.bsky.social
Kubernetes @ Apple | cert-manager maintainer | previously @ Jetstack
38 posts 1,389 followers 145 following
Regular Contributor
Active Commenter
comment in response to post
Oh wow, double or nothing I guess 🫣
comment in response to post
You didn’t show up for some reason!!! 😭🫶
comment in response to post
& of course the fabulous and just as regretful host… ā€œis this really what cloud native means?ā€
comment in response to post
Kind Ben!
comment in response to post
comment in response to post
case in point - you can’t not do things either
comment in response to post
To be fair, the naming is unfortunate!! ā€œBuilding a package from sourceā€ would be way clearer
comment in response to post
(md2man, but same point)
comment in response to post
Building from source there doesn’t refer to building the project though right? The project itself is used to build things from source. The example there is building gomd2json, and stepping through how to use the project to do so. Unless I am misunderstanding…. It is like 6am here 🫣
comment in response to post
I’m confused - you’ve linked to a detailed 4 page getting started guide right here? šŸ‘€ Or you mean specifically they only included a detailed page, not a basic one? (Interesting project though, thanks for the pointer!)
comment in response to post
This community has been the vast majority of my professional career and I am incredibly thankful for all of you. On the flight out here I was already looking at moving my flight home forward and hiding. Now, I am excited for the next couple of days ahead. From the bottom of my heart, thank you ā¤ļø
comment in response to post
From quiet dinners with those I only see a couple times a year, to meetings about project ideas, to 3 different groups of people coincidentally flooding into a pizza restaurant and suddenly excitedly chatting until the servers ask us to sit down as we started taking up the whole place..
comment in response to post
I cannot express how much it has meant to me. It has reminded me not only of the fantastic people around me, but also how much everyone cares for each other in this community.
comment in response to post
Yep exactly - one big scheduling domain 😊 tiered caches for scalability is optional/not required (though with caveats wrt consistent reads): github.com/kubernetes/k... Ideally, instead of caching, I want to improve performance of operations that select objects across namespaces within k8s 😊
comment in response to post
Next I’ll be talking with co-speaker Anish Ramasekar on securing node local agents like Cilium with validating admission policies to only allow mutating fields and objects associated with that node on Friday, 11.55am, 151G kccncna2024.sched.com/event/1i7qC/...
comment in response to post
First up, a talk on proxying apiservers to create the concept of workspaces, or ā€˜cluster scoped views’ across namespaces to enhance multi-tenancy use cases in Kubernetes on Thursday, 11am in 255B along with co-speaker Andrea Tosatto! kccncna2024.sched.com/event/1i7nS/...
comment in response to post
Welcome to London! 🄽
comment in response to post
+1 - tiring enough managing one personality let alone two 🫠
comment in response to post
Yeah I am really scratching my head. It makes so little sense it’s either truly idiocy with a (set of?) dictator(s) at the top, or the conspiracy theories actually might have some basis šŸ¤·ā€ā™‚ļø bizarre choice
comment in response to post
The temporary part is the most curious to me. What is so bad that it warrants damaging your credibility/brand for a small period of time and not just sucking up the $$?
comment in response to post
The whole thing just does not make sense to me from a money making perspective šŸ˜… how bad must this scraping be to cut off some hundreds of millions of users generating ad revenue? Kubernetes never shipped ads… but if it did, I don’t think it’d do it like this 😜 (wg-ads would need to convene first!)
comment in response to post
I’m really interested to see if this change did come as direct incident response, but (personally/anecdotally) didn’t see degraded service prior to the change… & rate limiting your entire read API for a weekend seems like a pretty big decision for oncall to make šŸ™ƒ
comment in response to post
šŸ’Æ it’s already far too easy to get lost in work (in tech, at least) without your leadership actively *encouraging* it & shipping features out of hours/on weekends. ā€Hustle cultureā€ is weirdly glorified all over. I’m all for people being passionate about their work, but it shouldn’t be top down.
comment in response to post
It takes patience and careful planning to view tweets nowadays šŸ‘ thanks for sharing, I certainly can’t see it myself šŸ˜„