sig-release VS examples

As Wednesday kicked off, it was great to feel the buzz and excitement of folks so eager to learn and connect. From Day 1’s keynote, I really enjoyed the reminder that companies benefiting from Kubernetes and the CNCF ecosystem should be getting involved, giving back, and mentoring others. There was a lot of love to maintainers and contributors in the ecosystem, and as someone involved in the Kubernetes Release Team for Kubernetes v1.25 and v1.26, it was a huge honor to see my face up in there with the rest of the team! 💙

Shout out to the SIG Release team once again for all of their hard work to ship 1.23. Release management is hard and often thankless work, and I appreciate their efforts so much. Also, I want to give a big thank you to everyone who contributed to 1.23. When I see such a long list of changes, it’s clear that many people worked hard to get them done.

Today the 1.22 version of Kubernetes ships. As always, hats off to the members of SIG Release for all of their hard work.

Here you go. https://github.com/kubernetes/sig-release/discussions/1877

Honeycomb

I haven't used anything else, but I'll gladly shill for https://honeycomb.io.

With all of this in place I went a step further and added Opentelemetry to track the stats of how often the routine was being triggered on Honeycomb.

Events can be used in many meaningful ways. The Event subsystem of B is pretty much a co-evolution of what honeycomb.io offers, but implemented completely differently - it is on bare-metal, and hence a lot cheaper. Because of that, B never subsampled, but always kept a full low of all events anywhere, no exceptions.

It should be noted that this is a very oblique ad for http://honeycomb.io. That in no way impugns the content of the post, and in fact, it's given the content of the post that I feel compelled to point out that, ultimately, this is an ad. Because what is sales and advertising, anyway? It's just a way to get you to buy a product, and you can't do that if you've never even heard about the product. I'm not currently in the market for an observability solution (something something splunk) but if I were, I've now heard of them.

The question though, is why does money ruin everything? The naive questions of an open source zealot to a proprietary software salesperson are one thing, but since we all need money to live, why does money being part of the equation (eg if someone was getting paid to post here) ruin things? Would a "donate to open source" button be more successful if the donate text is "buy me a coffee", "buy me a beer", or "upgrade my beer from Coors light"?

https://xkcd.com/2347/ was and is true, and if we don't figure out a way to change that, I don't really see a future for open source.

Very cool to see honeycomb.io is doing that. I'm about to embark on my distributed tracing learning journey, this makes me want to try honeycomb right away.

Caveat: I work for a vendor in the O11y space (https://honeycomb.io) as a Developer Advocate, however, this advice is generic, not specific to our platform.

I spent Day 2 at the Colony Club to attend OTel Unplugged. This event was sponsored by Lightstep, Honeycomb, New Relic, Splunk, Dynatrace, Crowdstrike, and NGINX. I came into the event not knowing what to expect. I can sometimes clamp up when I’m around folks that I don’t know, but because I was helping with the event check-in, I got to say hello to a number of the attendees, which helped break the ice. And it turns out that there were a lot of names that I recognized from my work in the OTel community, and it was nice to connect in person with folks whom I’d only previously met through Slack or Zoom.

It's no surprise that my apps are mostly written using Sanic as I'm pretty involved with the project. I've been wanting to start testing honeycomb out as well, so it seemed the perfect opportunity to try out.