so much rust
27.11.2025 17:27 β π 1 π 0 π¬ 0 π 0@cloudnativeyoda.bsky.social
post about star wars and cloud native things i do.
so much rust
27.11.2025 17:27 β π 1 π 0 π¬ 0 π 0yoda: "when 900 years old you are, thankful for every new day of life, you will be"
27.11.2025 17:15 β π 2 π 0 π¬ 0 π 0steer kubernetes better than han does the millennium falcon, kat will. yahoo!
05.11.2025 16:43 β π 1 π 0 π¬ 0 π 0like the dark side of the force, kubecon is always with us.
05.11.2025 16:40 β π 2 π 0 π¬ 0 π 0"death star plans briefing scene" title: vLLM Team Standup subtitle: Refactoring of the vLLM Semantic Routerβs Rust-based classification layer addresses this problem through architectural modularity, Low-Rank Adaptation, and concurrency optimization.
blog.vllm.ai/2025/10/27/s...
27.10.2025 15:10 β π 0 π 0 π¬ 0 π 0darth maul firing up his two-sided lightsaber. first side "anti-trans legislation". second side "mass shootings"
22.10.2025 09:00 β π 0 π 0 π¬ 0 π 0ChatGPT prompt: "What can I help with" Emperor Palpatine: "Use my knowledge, I beg you!"
18.10.2025 13:15 β π 1 π 0 π¬ 0 π 0the jar jar binks of software companies, atlassian is
08.10.2025 14:03 β π 3 π 1 π¬ 0 π 0Star Wars Episode X: Return to the Office
16.09.2025 04:06 β π 1 π 0 π¬ 0 π 0Darth Vader, thumbs up. βYou want how many billions of GPU capacity? you got it.β
16.09.2025 04:05 β π 0 π 0 π¬ 0 π 0on vacation i was. summer in dagobah yo.
> kyoob
"that's not a moon..."
04.08.2025 09:46 β π 2 π 0 π¬ 0 π 0Emperor shoots force lightning. Caption β Give in to the force of the bitnami subscriptionβ¦ it is the only way you will see your beloved containers and helm charts againβ
30.07.2025 07:56 β π 3 π 0 π¬ 0 π 0actually, replace you ai agents will. but if it helps you feel better, think of them as just tools to help you do your job. same the outcome, but happier you will be for a few months.
14.07.2025 20:37 β π 0 π 0 π¬ 0 π 0so much dark side. thank the force for cloud native yoda.
14.07.2025 20:22 β π 0 π 0 π¬ 0 π 0top panel: screenshot of an article titled "Kubernetes 1.33 release adds native support for container sidecars". Luke says "I don't believe it" bottom panel: Yoda says "That is why you fail"
native sidecars: proof of the force (of community)
14.07.2025 20:02 β π 0 π 0 π¬ 0 π 0a picture of Yoda waving a US flag, warming a hot dog on a stick, over a campfire
And for the support of this declaration, with a firm reliance on the protection of Prometheus and Grafana, we mutually pledge to each other our logs, our metrics, and our sacred uptime.
Deploy or deploy not, there is no try.
MAY THE FOURTH (OF JULY) BE WITH YOU!
That these services are, and of right ought to be, free and loosely coupled; that they are absolved from all allegiance to monolithic and proprietary solutions; and that all connection between them and legacy systems is and ought to be totally dissolved.
04.07.2025 18:04 β π 0 π 0 π¬ 1 π 0We, therefore, the representatives of the united microservices of Cloud Native, in General Assembly, appealing to the SREs of the world for the rectitude of our intentions, do, in the name and by authority of the good people of this ecosystem, solemnly publish and declare:
04.07.2025 18:04 β π 0 π 0 π¬ 1 π 0* It has dissolved network connections repeatedly, for opposing with manly firmness the http requests of the people.
* For cutting-edge features, it has declared feature flags, and toggled them without warning.
* It has forbidden Nodes to upgrade, unless suspended in their operation by a Cordon and appropriate Taint applied.
* It has erected a multitude of YAML files, & sent hither swarms of Helm charts to harass our junior Engineers.
* It has kept among us, in times of peace, sidecars without our consent.
The history of the present Kubernetes is a history of repeated injuries & usurpations.
Let Facts be submitted to a candid world:
* It has refused to autoscale, the most wholesome and necessary for the public good.
But when a long train of outages, memory leaks, and license audits, pursuing invariably the same Object evinces a design to reduce them under absolute vendor lock-in, it is their duty to throw off such tooling, and to provide new guards for their future deployments.
04.07.2025 18:04 β π 0 π 0 π¬ 1 π 0Prudence indeed will dictate that legacy systems long established should not be changed for light & transient causes; accordingly all experience hath shewn that engineers are more disposed to suffer, while bugs are sufferable, than to right themselves by abolishing code to which they are accustomed.
04.07.2025 18:04 β π 0 π 0 π¬ 1 π 0