hachyderm.io is one of the many independent Mastodon servers you can use to participate in the fediverse.
Hachyderm is a safe space, LGBTQIA+ and BLM, primarily comprised of tech industry professionals world wide. Note that many non-user account types have restrictions - please see our About page.

Administered by:

Server stats:

8.9K
active users

#Linkerd

0 posts0 participants0 posts today

Have you missed #KubeConEU in London this month?
I've got you covered!
Next week I'll run a #KubeCon recap live stream with my fellow #CNCF Ambassadors Kasper Borg Nissen (KubeCon Co-Chair) and William Rizzo (also a #Linkerd Ambassador).
Even if you've attended the event, you're bound to get cool insights 😉
And you can share your own on the live chat! and ask us questions!

🗓️ 22 April 2025, 11:00 CET, OpenObservability Talks:
🌐 youtu.be/JyxJOmOEBvQ

Progress report 3: Today I finally got #ArgoCD accessible via #Traefik’s IngressRoute on the IP assigned and announced by #Cilium. I'm now working on getting access via the #k8s Gateway API's equivalent. I’ve also gotten past all my #SELinux issues on @fedora #CoreOS… it took relabeling the entire file system post #K3s installation, but now Cilium, #Linkerd, and #Multus are all in without the use of elevated privileges.
[ #Linux #Kubernetes #Fedora ]

Progress report 2 on my #k8s setup centered around #K3s on @fedora #CoreOS: #SELinux is on & the #Cilium CNI, the #Linkerd CNI & service mesh, & #ArgoCD are installed! Both CNIs had to be installed with privileged=true, unfortunately… but at least it worked! Now to get a repo setup with all the charts and/or manifests needed to manage these components & others post-bootstrapping. Once all are effectively imported into Argo CD I’ll start adding more stuff.

Progress on my latest endeavor: I’m building a #k8s setup centered around #k3s, the #Cilium CNI, and the #Linkerd service mesh. My goal is to run this atop an immutable #Linux distro with #SELinux enabled. Sadly, the Cilium bits don’t work with @fedora #CoreOS without disabling SELinux even without Cilium’s Envoy daemonset. Barring some breakthrough in figuring out why that is, I’m planning to try @opensuse #MicroOS next. Its use of btrfs is quite appealing.

Replied in thread

@marcus_grant Yes, clarifying mutual expectations is good. If a contract on top of the license helps, so be it.

I'm not convinced it's primarily a legal issue: to this day, if you're a self-hosted user of #HashiCorp #FreeSoftware, you have no way to throw money at HashiCorp even if you want to.

Same with the #linkerd fiasco (github.com/cncf/toc/issues/126): did Buoyant ever ask help from #CNCF or anyone before cutting off the supposed free-riders?

Maybe the VC playbook doesn't fit collaboration.

GitHubHealth of Linkerd project · Issue #1262 · cncf/tocBy dims

I've been thinking a lot about the #linkerd news today. I've been sitting on a pile of research and tutorials and am planning on running a PoC with it, but the news (and the responses around it) added a surprise bit of chaos to my plans.

I understand everybody's "but wait, opensource" anger, but I do think we're seeing lots and lots of companies and tools that were traditionally assumed as free making a point that actually it's _not_ free to do all of this work.

While I’ll be following the / drama with interest, this isn’t a rug pull like the license switch. means the source code is… well, open. That’s *all*. I’ve said it before: there’s no “spirit of open source” that always seems to put a ton of obligations on maintainers but never on users.

Doesn’t mean anyone has to be happy about the change, and I fully understand those who aren’t. But if it’s not in a license — OSS or commercial — it’s not an obligation.