usrbinkat
@usrbinkat.io
4K followers 5.2K following 4.1K posts
🧙‍♀️ Open Sourceress 🚀 Ms. (f)Rizzle @Cisco 🏳️‍⚧️ Blame for Oops & Ops my own 🤗 Seize the means of computing 👩‍💻 K8s/AWS/Azure Platform Engineer 📖 https://blog.usrbinkat.io/en/page/about 🍿Watching Dystopia IRL 🧠 Neuro Spicy Autist 📍 Sacramento ☀
Posts Media Videos Starter Packs
Pinned
usrbinkat.io
Obstruct Injustice
usrbinkat.io
🪄💻🔮✨

Hubble so sassy, responded with like "not serving"..

Hubble dramatic.
usrbinkat.io
Happy birthday 🎁🎈🎂🎉
usrbinkat.io
Open sourcery 🪄🔮🫧✨
usrbinkat.io
Same! heavy jq user, tried sifting through this prometheus values.yaml though and 5K+ lines was too much. I'm not even to rook ceph charts yet.

I think I just needed muscle memory to need a reason and this is def a use case.
usrbinkat.io
TIL yaml taming!

`~$ yq -c . foo.yaml`
Terminal screenshot shows the command `yq -c . ./workspace/infrastructure/pulumi/helm-chart-kube-prometheus-stack.77.12.0.yaml` being run, which outputs the entire YAML file as a single compact JSON line. The file path and name appear twice—first in a `wc -l` command showing 5434 lines, then with `yq -c`, collapsing those lines into a densely packed, color-coded output. The shell prompt shows the workspace on the `main` branch, using Node v24.9.0 and Python v3.13.7, inside a Docker context.

This demonstrates a common developer technique for visually taming massive YAML files by using `yq -c`, which transforms verbose configuration into minified JSON for quick scanning, jq parsing, grepping, or debugging.
usrbinkat.io
Fuck ya fuck ya fuck ya ya ya ya yessss
usrbinkat.io
She's so fun to fly.

I have a multi-root workspace setup with all of the CI in `actions`, my iac is all centralized in `infrastructure`, etc etc. my workflow is containerized and automated in devcontainers and mise. Can't wait to start deploying & developing the app code.

I feel like a pilot :D
usrbinkat.io
Yesssssss <3
usrbinkat.io
Minecraft Saturday :D

It's a sugar cane farm that produces paper for a gunpowder + paper auto-fireworks farm. Now just need to finish glam'ing it up to look pretty next to the Iron farm.

1/n

#Minecraft #PaperFarm #Redstone #MinecraftAesthetics
The image is a screenshot from Minecraft showcasing a complex two-story sugarcane farm built over a body of water. The farm is fully automated, using minecarts, hoppers, comparators, and redstone circuits to harvest and process sugarcane into paper. This paper is later combined with gunpowder from a nearby, unseen gunpowder farm to produce fireworks for Elytra flight.

### Functional Details:
- The sugarcane farm uses observers and pistons to detect and automatically harvest the sugarcane when it grows.
- Harvested sugarcane is transported via minecarts with hoppers into a storage or crafting system.
- The redstone contraptions visible suggest efficient automation and integration with a larger item processing pipeline.

### Aesthetic Observations:
- The farm features a vibrant and structured design, blending deep slate blocks, crimson and warped wood, and lanterns for lighting. This gives the structure a mystical, industrial theme.
- Decorative blocks, such as sea lanterns, stained glass, and banners, add visual depth and a cohesive design language to the build.
- Adjacent to the sugarcane farm is another structure, possibly a work in progress, with a similar palette and thematic style, indicating a planned cohesive build area.
- The surrounding water is decorated with lily pads and floating campfires, enhancing the atmosphere and giving a naturalistic yet magical vibe.

The view illustrates both the technical sophistication of the farm’s automation and the effort put into creating an aesthetically pleasing environment in Minecraft.
usrbinkat.io
I've been tempted into trying rancher desktop, podman, podman desktop, exclusively using a remote linux machine or VM, using just WSL, nerdctl, etc etc.

I'm extremely container dependent and use quite a few niche features. Devcontainer and other useses do not play nice with other docker providers 😢
usrbinkat.io
What's in your Docker Desktop?
Full-screen screenshot of VS Code in a dev container titled “Cisco Security @ desktop-linux,” showing a deeply integrated infrastructure-as-code (IaC) Kubernetes environment in active development. Top left is the Pulumi stack YAML config defining a Talos-based local Kubernetes cluster, launched with Docker Compose. Top center is k9s terminal UI displaying pod health for all namespaces in the Talos cluster, including cert-manager, kube-system, and kubevirt workloads. Bottom left shows Python source code for a custom Pulumi component, `HostPathProvisionerComponent`, declaring Kubernetes resources via Pulumi’s Python SDK. Bottom right terminal displays the output of a Pulumi preview, showing resource updates for RBAC roles, CRDs, and secrets being deployed. The workspace is running on branch `main`, Python v3.12.7, Node v24.4.1, and the prompt reflects a Dockerized environment orchestrated with `mise`.

This stack uses Pulumi to declaratively deploy infrastructure into a locally composed Talos cluster, with YAML and Python working in tandem to build modular Kubernetes components. The user is clearly working in an advanced iterative loop: stack configuration is open for editing, IaC logic is visible and modularized, resources are actively being deployed, and k9s gives immediate visual feedback from the live cluster—all within a single devcontainer setup. This is a tightly bound feedback loop between definition, execution, and state verification.

Together, it reflects a highly optimized development flow where modern IaC principles meet security-conscious Kubernetes experimentation. This isn’t just code—it’s a reproducible cloud lab running in Docker Desktop. When someone asks, “What’s in your Docker Desktop?”—this is the answer: a real-time, local-first control plane that can bootstrap, mutate, and tear down complex Kubernetes systems on command, with total infrastructure transparency at every layer.
usrbinkat.io
*one of us, one of us, one of us*

make the wobots go brrr
usrbinkat.io
OMG first time I'm actually deploying kubernetes pods in like, 6 months!

Today is going to be a fun day.

Happy Tuesday peeps 🐤🐤🐤
usrbinkat.io
The developer hell is an eternal unresolvable dependency nightmare.
usrbinkat.io
When you want to develop a nix flake but you want development to be easy in codespaces.

Say hello to Systemd in Debian 13 Trixie Docker Compose based Devcontainer on GitHub Codespaces remote development environment. Connected via VSCode Remote Containers extension.

Philosophically impure 💀
A Visual Studio Code window with dark theme is open on macOS, connected to a GitHub Codespace for the repo “kalilix.” The left tree shows files like flake.nix, devcontainer.json, docker-compose, setup.toml, and .config/mise for task automation. The center terminal shows logs from a devcontainer running docker.io/library/debian:trixie (Debian 13) with nix installed. Output includes systemd startup, a process tree with /lib/systemd/systemd, nix develop, dbus-daemon, nix-daemon, and vscode-remote processes, ending with “Outcome: success” and “Finished configuring codespace.” The right terminal runs nix flake show inside the shell “kalilix-base-env,” listing devshells for aarch64-darwin, aarch64-linux, x86_64-darwin, and x86_64-linux, with omitted entries for python and rust, plus overlays including Nixpkgs. Git remote -v confirms origin at github.com/usrbinkat/kalilix.

Technically, this shows a flake-managed devcontainer built with Docker Compose. Nix flakes handle dependency management, mise replaces Make for workflow automation, and the flake defines multi-arch devshells with overlays for polyglot development. Systemd runs in the container, enabling nix-daemon, dbus, and vscode integration. Logs confirm deterministic startup through flake shell availability.

Overall, the screenshot illustrates how kalilix provides a reproducible Kali Linux–style dev environment on nix. All dependencies and overlays are versioned in the flake, ensuring consistent builds across Darwin and Linux. By pairing nix for package management with mise for tasks like linting, testing, and lifecycle updates, the project treats environments as code, giving teams a single repeatable foundation for development and CI.
usrbinkat.io
Oof idk not till i have at least some baseline success to build from. Maybe at some point tho
usrbinkat.io
Still waiting on the ultimate question.
usrbinkat.io
She's gotta be one of my all time favorite characters.