While many #opensource companies are abandoning the open-source approach, #Kubernetes and #OpenStack powerhouse MirantisIT is embracing it more than ever.
I’m still processing everything, but I noticed some commonalities in the kinds of challenges #contributors are facing during this 2024 lonely burnout epoch (I’m not the only one who feels it right?)And I wonder if more #maintainers are facing them too.
So what are the toughest #community/ communications/ outreach challenges you’re tackling?
In the latest episode of our 20 minutes Cloud Commute podcast, @boredabdel talks about serverless platforms and the complications with GPU workloads; as well as anything #kubernetes, #gke, #cloud, #docker and more 🔥
I’m using the #tailscale#kubernetes operator for my #k3s cluster, and I would like for one particular workload to use a specific exit node. I don’t think that’s possible today via the operator, but does anyone know what change would be? Do I need a tailscale sidecar container on my workload pods?
Anyone have a preferred method for copying data out of a Kube PV?
EDIT: I have a PV filled with nextcloud uploads and I want to copy it out. I know I can simply kubectl cp it or other tricks but looking for something more…appropriate
I kept my twtr account for a while because brands I occasionally reach out to were still exclusively there. It’s now no longer the case so I put the account down for real :)
Kubernetes is a household name in the cloud native world. OKD is a community distribution of Kubernetes, and you can run it locally with CRC! Great for playing with a more rounded out container platform than what Kubernetes does on its own.
Anyone familiar with terraform, GKE and enabling GCP services from TF?
Setting up a new project and trying to plan a GKE cluster. But I get this response saying the Kubernetes API hasn't be used or is disabled - well yes, it's a new project. But it's listed in the services for the project and should then get enabled like all the others, right 🤔
Google just asked if we could enable via the UI. But that's not the point. This is meant to be automated with TF.
In her opening keynote at KubeCon + CloudNativeCon Europe in Paris, Priyanka Sharma, executive director of the Cloud Native Computing Foundation (CNCF), spoke of AI being in an "irrational exhuberance" phase, meaning that expectations are moving well ahead of delivery.
They only provide a Dockerfile because it's so convoluted and patched together that it would be impossible to create a decent guide on how to make this stuff work without revealing just how much it's all held together by duct tape. Still, taking a peek at the Dockerfile will clearly reveal the chaos at play.
Everything runs in separate containers, as it should, and they have automatic restarts, as they should. But then they're so tightly bound together with, you guessed it, duct tape, that when one of them fails, the container just restarts automatically, leaving the user wondering why everything failed, with only a cryptic error message.
The main container is controlled by Supervisor - which is necessary because everything crashes very often, but the end user doesn't notice because Supervisor restarts the services. To outsiders, everything works fine (but occasionally throws some errors).
In short, the current trend is to sweep the dirt under the rug. A trendy rug, though!