Recent searches

No recent searches

Search options

Only available when logged in.
shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

251
active users

shakedown.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.3

#k8s

4 posts2 participants0 posts today
"Musty Bits" McGee<p>Good overview of cgroups in the Kubernetes context with nice examples</p><p><a href="https://martinheinz.dev/blog/91" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">martinheinz.dev/blog/91</span><span class="invisible"></span></a></p><p><a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a></p>
"Musty Bits" McGee<p>Interesting article on measuring pressure instead of utilization for Kubernetes</p><p><a href="https://blog.zmalik.dev/p/from-utilization-to-psi-rethinking" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.zmalik.dev/p/from-utiliza</span><span class="invisible">tion-to-psi-rethinking</span></a></p><p><a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a></p>
"Musty Bits" McGee<p>Oauth working for Kubernetes authentication and authorization.</p><p>Very satisfying, if fiddly.</p><p><a href="https://eigenmagic.net/tags/HomeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HomeLab</span></a> <a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> <a href="https://eigenmagic.net/tags/Oauth" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Oauth</span></a></p>
"Musty Bits" McGee<p>Cool blog spotto</p><p><a href="https://blog.stonegarden.dev/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">blog.stonegarden.dev/</span><span class="invisible"></span></a></p><p><a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://eigenmagic.net/tags/OIDC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OIDC</span></a> <a href="https://eigenmagic.net/tags/Oauth" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Oauth</span></a> <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> <a href="https://eigenmagic.net/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Proxmox</span></a> <a href="https://eigenmagic.net/tags/Talos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Talos</span></a> <a href="https://eigenmagic.net/tags/TalosLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TalosLinux</span></a> <a href="https://eigenmagic.net/tags/ArgoCD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ArgoCD</span></a></p>
Shoshana 🏳️‍⚧️<p>How do you pronounce kubectl?</p><p><a href="https://tech.lgbt/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kubernetes</span></a> <a href="https://tech.lgbt/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a></p>
"Musty Bits" McGee<p>The new Kubernetes mount-an-OCI-artifact feature got me thinking about backups, layers, data locality, and deduplication via CAS.</p><p>Imagine using image layers as snapshots and pushing images as your application's data backup. Then by specifying latest* for the volume mount it would automatically come up with eagerly-cached, local data.</p><p>I don't think CAS helps our case for storage here as a layer-snapshot mapping isn't granular enough. Of course it's not like you'd want to redesign your Postgres paging configuration entirely around a better mapping to image layers but there's something there...</p><p>Registry-side you could do periodic compaction, archival, export etc.</p><p>OCI image layers are already limited though last time I checked. Nix maps derivations (think packages) to layers and neither OCI nor the tooling were designed for that kind of blowout. Could be tackled though.</p><p>*yes yes, anti pattern. Hold ur underwear a moment.</p><p><a href="https://eigenmagic.net/tags/OCI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OCI</span></a> <a href="https://eigenmagic.net/tags/Containers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Containers</span></a> <a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> <a href="https://eigenmagic.net/tags/PlatformEngineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PlatformEngineering</span></a> <a href="https://eigenmagic.net/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DevOps</span></a> <a href="https://eigenmagic.net/tags/Cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cloud</span></a> <a href="https://eigenmagic.net/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Docker</span></a></p>
"Musty Bits" McGee<p>Oh that's so cursed</p><p><a href="https://github.com/llmnetes/llmnetes" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/llmnetes/llmnetes</span><span class="invisible"></span></a></p><p><a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a></p>
"Musty Bits" McGee<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@seanhood" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>seanhood</span></a></span> there's a few key changes in my design<br>1. A full, functional programming language for inflating configuration into manifest files. We publish a versioned library of this as an OCI artifact, and any resources or changes the library doesn't support yet can be done by passing a closure/function to an escape hatch.<br>2. Kubernetes is THE control plane. Anything that would have been terraform is now Crossplane or ACK or whatever operator. No living in two worlds or picking the best-of-the-worst couplings between TF and K8s <br>3. The control plane desired stare should include any cross-resource dependencies. It's still GitOps but there should be no need for any write back or chore commits. This is where the custom operator comes in, though potentially Kro could work.</p><p><a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://eigenmagic.net/tags/KubernetesDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>KubernetesDev</span></a> <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> <a href="https://eigenmagic.net/tags/k8sDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8sDev</span></a></p>
"Musty Bits" McGee<p>Volume mounts from OCI targetting v1.34 </p><p>Ed. Might be 1.35</p><p><a href="https://github.com/kubernetes/enhancements/issues/4639" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/kubernetes/enhancem</span><span class="invisible">ents/issues/4639</span></a></p><p><a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a></p>
"Musty Bits" McGee<p>Interesting but what-you'd-expect container caching enhancement to Kubernetes architecture.</p><p>Does make me wonder if you could do the caching at the content-addressed-storage layer with distributed s3 and data locality via redirects and maybe presigned URLs...</p><p><a href="https://www.youtube.com/watch?v=trFILyK6mPw" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/watch?v=trFILyK6mP</span><span class="invisible">w</span></a></p><p><a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> <a href="https://eigenmagic.net/tags/KubernetesDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>KubernetesDev</span></a> <a href="https://eigenmagic.net/tags/k8sDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8sDev</span></a></p>
"Musty Bits" McGee<p>KwoK is hilarious to me. Like I *get* why it exists it's just funny to take the ONE, *absolutely* necessary program for a cluster and be like "naaah, we'll mock it"<br><a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> <a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://eigenmagic.net/tags/k8sDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8sDev</span></a> <a href="https://eigenmagic.net/tags/KubernetesDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>KubernetesDev</span></a></p>
"Musty Bits" McGee<p><span class="h-card" translate="no"><a href="https://learnk8s.news/@learnk8s" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>learnk8s</span></a></span> Helm does what it set out to do quite well. I'm skeptical that v4 will be able to break free enough of the paradigm it's established to provide a novel enough solution to the challenges that have arisen since v2. <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> <a href="https://eigenmagic.net/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kubernetes</span></a></p>
"Musty Bits" McGee<p>What's that phenomenon where the mate withers and becomes a parasite on the other's body?</p><p><a href="https://eigenmagic.net/tags/etcd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>etcd</span></a></p><p><a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> <a href="https://eigenmagic.net/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kubernetes</span></a> <a href="https://eigenmagic.net/tags/kh8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kh8s</span></a></p>
jbz<p>｢ Docker is essentially a sandwich of disk images where you can shove absolutely anything, and then these images get executed by running whatever legacy software you’ve crammed in there, regardless of how horrific or inconsistent it might be, with zero behavioral controls ｣ </p><p><a href="https://indieweb.social/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> <a href="https://indieweb.social/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>docker</span></a> <a href="https://indieweb.social/tags/containers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>containers</span></a><br><a href="https://andreafortuna.org/2025/06/20/unpopular-opinion-kubernetes-is-a-symptom-not-a-solution" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">andreafortuna.org/2025/06/20/u</span><span class="invisible">npopular-opinion-kubernetes-is-a-symptom-not-a-solution</span></a></p>
Not🐧A🐧Convicted🐧Felon<p><span class="h-card" translate="no"><a href="https://mastodon.functional.computer/@samir" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>samir</span></a></span> Every single day a team of 25 people is kept busy running a <a href="https://hachyderm.io/tags/K8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>K8s</span></a> cluster with 1200 nodes, that actually could be replaced by less than ten 1U machines using a system design that actually solves the 10K problem, instead of one that struggles to handle even 10 req/s.<br>This is the vicious cycle of technical debt. </p><p>This week's problem: cluster-autoscaler has a bug that causes machines that start up to get stuck in a zombie state without successfully registering with the control plane. This causes all kinds of cluster scale up issues, especially with multi-AZ workloads.</p><p>Every week is a new bug, a new edge case, a new issue with dependencies (K8s, helm, Rancher, Istio, etcd, ...) a new issue with AWS, it just goes on and on.</p><p>I yearn for the days of simplicity of just running servers in racks and you're like "oh, had another hard drive failure in rack 04, have to go swap out a HDD cartridge and rebuild the RAID".</p>
Mika<p>My <a href="https://sakurajima.social/tags/homelab" rel="nofollow noopener" target="_blank">#homelab</a> wiki is getting really complicated to organise and write for haha, but it's definitely getting more interesting topics like more <a href="https://sakurajima.social/tags/RaspberryPi" rel="nofollow noopener" target="_blank">#RaspberryPi</a> stuffs, <a href="https://sakurajima.social/tags/Docker" rel="nofollow noopener" target="_blank">#Docker</a>, and some cool stuffs like <a href="https://sakurajima.social/tags/OpenMediaVault" rel="nofollow noopener" target="_blank">#OpenMediaVault</a> and <a href="https://sakurajima.social/tags/HomeAssistant" rel="nofollow noopener" target="_blank">#HomeAssistant</a>. I'm taking my sweet time to update them 'properly' and hope it'll all link/piece together <i>sensibly</i><span> in the end.<br><br>This is partially thanks to me embracing the fact that I just don't (yet) have the resources for a </span><i>standalone</i> 'mega' homelab (<a href="https://sakurajima.social/tags/Proxmox" rel="nofollow noopener" target="_blank">#Proxmox</a> &amp; <a href="https://sakurajima.social/tags/Kubernetes" rel="nofollow noopener" target="_blank">#Kubernetes</a><span> based) server cluster that I could simply throw everything to it, hence supplementing that setup with tinier SBC-based servers. Gives me a bit of peace of mind too that things are now more 'spread out'.<br><br>The most interesting bit will probably be when I manage to explore replicating a mini version of my </span><a href="https://sakurajima.social/tags/RKE2" rel="nofollow noopener" target="_blank">#RKE2</a> Kubernetes cluster, on a single (or at most, two) Raspberry Pi node - maybe based on <a href="https://sakurajima.social/tags/k3s" rel="nofollow noopener" target="_blank">#k3s</a>, assuming that's better. I'm just not there yet cos I'm kinda reluctant if using something like <a href="https://sakurajima.social/tags/k8s" rel="nofollow noopener" target="_blank">#k8s</a> on RPi makes much sense since I'm expecting a lot of resources will be wasted that way, when hosting on Docker alone (i.e. on <a href="https://sakurajima.social/tags/Portainer" rel="nofollow noopener" target="_blank">#Portainer</a>) <i>should</i><span> be leaner.<br><br></span>🔗 Anyway, if y'all wanna keep an eye on it: <a href="https://github.com/irfanhakim-as/homelab-wiki" rel="nofollow noopener" target="_blank">https://github.com/irfanhakim-as/homelab-wiki</a></p>
"Musty Bits" McGee<p>God damn this ACK controller is fucking broken.</p><p>It grabs a list of all endpoint services - just any of them, no need to filter or match on anything. What's that? You provided a unique primary key? Bwahahaha</p><p>Then it takes any fields off the first one listed as canon. No diffs, no looking at all the options, just "does this have not-nil? take it".</p><p>Then it blats anything on your resource with those values, and calls it done. You literally cannot have more than one endpoint service per AWS region it's so broken.</p><p>Oh and it's broken for adopting existing AWS resources too.</p><p>Weh.</p><p><a href="https://github.com/aws-controllers-k8s/community/issues/2547" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/aws-controllers-k8s</span><span class="invisible">/community/issues/2547</span></a></p><p><a href="https://github.com/aws-controllers-k8s/ec2-controller/blob/09d198e3cc30ba644e6ead27513fbfaf48f67440/pkg/resource/vpc_endpoint_service_configuration/sdk.go#L93" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/aws-controllers-k8s</span><span class="invisible">/ec2-controller/blob/09d198e3cc30ba644e6ead27513fbfaf48f67440/pkg/resource/vpc_endpoint_service_configuration/sdk.go#L93</span></a></p><p><a href="https://eigenmagic.net/tags/AWS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AWS</span></a> <a href="https://eigenmagic.net/tags/ACK" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ACK</span></a> <a href="https://eigenmagic.net/tags/AWSACK" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AWSACK</span></a> <a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a></p>
"Musty Bits" McGee<p>Kubernetes curly: deployment with autoscaling, each pod depends on and occasionally writes-to an external database.<br>To minimise database reads, an in-memory cache is implemented in the application.</p><p>However, when a pod writes to the database it should invalidate that key in the cache for all pods.<br>This works fine for the local cache, but how to distribute that invalidation?</p><p>I suppose we could use a statefulset and then hit the service for each other running pod but that seems... messy.</p><p><a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> <a href="https://eigenmagic.net/tags/PlatformEngineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PlatformEngineering</span></a></p>
"Musty Bits" McGee<p>Anyone know if `system:apiserver` user should be allowed `create` action on `nodes/proxy`?</p><p>It's supposed to be the well-known user for the API server as a client to the kubelet (see source link) but it sure seems to be failing. I'd prefer not to just give system:masters</p><p><a href="https://github.com/kubernetes/kubernetes/blob/60a317eadfcb839692a68eab88b2096f4d708f4f/staging/src/k8s.io/apiserver/pkg/authentication/user/user.go#L78" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/kubernetes/kubernet</span><span class="invisible">es/blob/60a317eadfcb839692a68eab88b2096f4d708f4f/staging/src/k8s.io/apiserver/pkg/authentication/user/user.go#L78</span></a></p><p>`Internal error occurred: unable to upgrade connection: Forbidden (user=system:apiserver, verb=create, resource=nodes, subresource(s)=[proxy])`</p><p><a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> <a href="https://eigenmagic.net/tags/K8sAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>K8sAdmin</span></a> <a href="https://eigenmagic.net/tags/KubernetesAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>KubernetesAdmin</span></a></p>
"Musty Bits" McGee<p>This is quite elegant actually. <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> <a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a></p><p><a href="https://mastodon.social/@lobsters/114704587910809347" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mastodon.social/@lobsters/1147</span><span class="invisible">04587910809347</span></a></p>
TrendingLive feeds
About