How to connect your public environments across clouds and into your datacenter infrastructure – using official options, VPNs and new ideas like mTLS. Plus container networking, CNIs and other ways to plug extras into Kubernetes.
#PlatformEngineering
Meet us on the KubeTrain, at the KubeTrain Party, at the Swiss Apéro or anywhere around KubeCon to talk about Kubernetes, OpenShift, Servala, platform engineering, digital sovereignty and cloud native operations.
https://www.vshn.ch/en/blog/vshn-at-kubecon-europe-2026-in-amsterdam-we-look-forward-to-seeing-you/
We look forward to seeing you in Amsterdam and to connecting with the community once again.
#KubeCon #KubeConEurope #CloudNative #Kubernetes #OpenShift #PlatformEngineering #DigitalSovereignty #OpenSource #VSHN #Servala
Check out the latest #InfoQ #podcast featuring LinkedIn’s Karthik Ramgopal and Prince Valluri as they discuss scaling #AIagents in the enterprise, MCP, secure orchestration, and improving dev experience.
🎧 Listen now: https://bit.ly/4q5QR8G
Tomorrow we ride at dawn
Tomorrow's training agenda:
[I'm really liking these CodeWindows BTW - just little peeks at your real files so the 🪿 don't decide to apply their own brand of middleware on the way through when they're writing your notes]
#engineering #platformengineering #teachingthought #teachingcommunity
Y'all built a CLI Jenkins console log tailer too right?
So much nicer without all the noise they throw in (does anyone care that [pipeline] did a thing again)
And colours
This was a while ago though... I think I can do better
The 👶🏻🪿 (a wee GPT we pull in for transcript summaries of our training session) has spoken:
Today's training summary:
#OverloadProtection is one of the most overlooked practices in #PlatformEngineering.
The result? A fragile patchwork of inconsistent fixes across teams.
Centralized rate limits, quotas, adaptive controls, and real-time visibility give services predictable ways to absorb traffic spikes, reduce reliability debt, and prevent cascading failures across systems.
Learn more on #InfoQ 👉 https://bit.ly/48y5Bak
Did you miss Charlotte, Matt, and me talking about #GitOps #PlatformEngineering and #Compliance at SHIPPED25?
You can watch on demand here:
And then another one, a single pipeline orchestrating all of the stages, two AMI builds for the two tiers, rolling, controlled deployments of the front and back, full automation of the HAProxys' views of their target backends - all packaged up itself in a single file that describes both preproduction and production releases. The ultimate in testing your release automation, the configuration itself is DRY between environments, a slide rule window over the context that fills the voids the only difference.
[my other baby, a baby eagle called Peregrine - my developer platform and I'm quite proud of her]
The fact that they had all of this sitting right in front of them and decided that the thing to do was call me... might be why all the rest of that #wanderland nonsense is normally what I'm posting 🪿🧸🌱🎩💜
#devops #platformengineering #ileftanoutageforthis #witheverythingtheyneeded #neuroawesome #nomoreburnout
Oh yeah, I left an outage call to come work on this.
I mean, I left a technical DevOps manager, a DevOps engineer, a Lead Software Engineer and a Principal Technical Architect with a screen shot of the launch template and a big arrow pointing at the version to roll back to.
I don't even own the system, I just happen to like the guy that did and I helped him setup the automation. It's slick, two tier Shibboleth + HAProxy with redundancy on the front end and active/passive failover on the Shibboleth tier.
Each component has it's own deployment configuration. A single YAML that describes the process from little baby Packer template to the fully formed AMI that's cloned into the production environment. All the bits and bobs, URLs, pointers to infrastructure templates. Everything you'd need to know to deploy the thing (since it's how the thing is deployed... where else would it be?)
#engineering #platformengineering #devops #ileftanoutageforthis #witheverythingtheyneeded
We're still doing that thing where we feed the transcripts of our training sessions back into our knowledge graph to compare to the projected agenda for the day?
Make sure we cover everything before we plan the next day's agenda?
Feed it through your in house AI API to extract our the salient details for free? (to you anyways).
Just cuz you setup all their pipelines on your developer platform and they showed you how to get an auth token?
Just cuz you keep telling them that they can cache their huggingface models on shared storage and not keep baking them into the image they're deploying to Fargate that now takes an hour to bake and almost as long to start up when they need to scale?
(TMI?)
We're still doing that right cuz it's neat.
[Takes longer to fix the permissions on the transcript in sharepoint than it does to perform the analysis and feedback loop]
Y'all are going about this all wrong BTW with your silly little sandboxes.
Just do it once.
The documentation is the code is the test is the proof.
Markdown as the AST for functional, Turing complete YAML.
The YAML already compiles to Bash, why not through an intermediate "description" in there that's a bit more literal than most.
YAML pipeline definition compiles to fences containing the command definitions that would have fed direct to our CommandBuilder, now on a slight detour. Mixed in with a bit of delicious prose that describes the activity itself (@Narrative annotations FTW) and we're got an interesting solution to the problem of "just what the heck is that wall of YAML doing anyways?"
[describing the full end to end lifecycle of your software is usually the answer. from feature branch embryo through to production release. one file. build, image, deployment, test, publish. it's rather lovely]
#engineering #firstthingtomorrowtodayisfortheelephants #programming #platformEngineering
After a few weeks of getting dusty on my desk, today I finally started reading the #PlatformEngineering book—because a bunch of Snowflake clusters isn’t a platform. Thanks @skamille
Last night's Block Factory game this morning became Wanderland's IDE and needed thematic correction - we're encapsulating the idea of progressive enhancement in the narrative of Jack and the Beanstalk (because it's lovely, apt, and I like it :)) - so we're rebranding the game as Sprout Garden.
The two algorithms that drive it's game loop also drive Wanderland's workflow engine (or they will, once we've got the pattern established - that is the entire idea right?) follow the theme. Anyone can understand how we keep a distributed workflow on the rails if they can understand the game Hot Potato and a rather unfortunate concept I've lovingly rebranded in the hopes that no one thinks to hard about where it came from.
Then it gets fun, it's just little wiggly tiles right? With some shapes moving over them?
When it's a Jenkins pipeline, why not make it like Monopoly? I choose the 🚂
Anyone else driving an MCP that looks like this?
There's a language just in the 📍s.
#ai #humantools #engineering #platformengineering #engineeringcomfort
It feels good to be seen ;)
[and yes I know... I'm writing for you lot not for me... and for my boss so he knows I shipped something useful...]
If they can't figure out what to do with a fence that pulls a list of jobs from a named view, a fence that parses and pulls the configuration from a job from a job name alone (we have like 40 servers) and a fence that pulls it's build info (logs, status, all the bits - I did that one a few days ago on the little things blog) also from just a job name then...
Anyone hiring?
No magic - just engineering. 🛠️
Platform Engineering: how to build an Internal Developer Platform that doesn’t collapse on Friday night.
Guide here 👉 https://www.heyvaldemar.com/platform-engineering-internal-developer-platforms-complete-guide/
Well.. almost too late.
Wanderland is like Civ (like 4 or 5, before they got a bit like what Corey Doctrow's been talking about lately)... sometimes you unlock a new skill and you just need one more turn
I've been waiting for this one to unlock since I first starting thinking about oculus a month or so ago - attention based computing to go with computational markdown.
I mean, it's right there so why wouldn't you? 50 lines away means the abstraction has stayed clean since the inception.
Because it is.
Welcome to gardening Wanderland style - it's wonderfully weird here and I 💜 it
🧸🪈🎵 🪿🪿🪿🪿🪿🪿🪿🪿
#ai #platformEngineering #engineering #startedfromthebottomnowwerehere #didhejustdropadrakereference #itsokhescanadiananditwaseitherthatorironicagain
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst