@jschnatterer

No longer active on Twitter or what is left of it.
Account remains here for historical purposes only.

[John McBride @johncodes]

The most surprising thing about working at AWS was how much bash glue there was.

Good shell scripting: incredibly underrated skill.

[@jschnatterer @jschnatterer]

It's also worth mentioning that Flux recommends this pattern for it's OCI artifacts feature, without using the pattern name, yet 😉
https://t.co/qrqLks8vVQ

4/4

[@jschnatterer @jschnatterer]

On #GitOpsCon EU yesterday, I learned from @christianh814 that there is a pattern name for rendering your Kubernetes Manifests (Helm, Kustomize, JSonnet, CueLang, Timoni, etc.) on the CI server before deploying them via #GitOps: "Rendered Manifests" 👏
1/

[@jschnatterer @jschnatterer]

I especially like having a name for this pattern, because we have been using it ever since we migrated from Flux v1 to Argo CD in 2020.

💡 We also provide some examples on how to implement it in the GitOps playground:

https://t.co/VkBqRqWe8S

3/

[@jschnatterer @jschnatterer]

@schakko The devops Institute's value stream reference architecture calls those teams "Value Hives".

A lot of people seem to consider them as "real" full stack or devops teams 😀

https://t.co/fcB9CsxlV1

[@jschnatterer @jschnatterer]

Twitter bubble: How would you call a team that operates its whole tech stack by themselves?

For example you as a team get handed the admin credentials to a cloud account or project and can use what ever suits your business needs best.
1/3

[@jschnatterer @jschnatterer]

@schakko Yeah, naming things!

I also came to the conclusion that autonomous per se can mean much more than I intended.

My compromise is "technically autonomous".

There was quite a discussion on LinkedIn.
For the authors of team Topologies this is just a steam aligned team.

[@jschnatterer @jschnatterer]

Some ideas: "fully autonomous teams " or maybe "full-stack teams".
3/3

[@jschnatterer @jschnatterer]

No ops or platform team handles it for you. But there might be some form of inner consulting available that helps you get started.

I see that as a kind of counter concept or opposite of "platform engineering", without saying it's better or worse.
2/3

[@jschnatterer @jschnatterer]

Absolutely delighted to share that the #GitOps Playground now runs on Mac, Windows and Linux.

https://t.co/aZFGWmRrge

Create a complete GitOps-based operational stack including Kubernetes on your machine with only one command 🤯

👇️

[@jschnatterer @jschnatterer]

The whole talk in one slide 💡

[@jschnatterer @jschnatterer]

The magic quadrant between stability, features and
... Dependency updates on #ConLife23 by @NicholasDille @con

[@jschnatterer @jschnatterer]

Final advice by @schlomoschapiro @co #ConLife23

[@jschnatterer @jschnatterer]

Day 2 of @ConLifecycle kicks off with @schlomoschapiro motivating for possessing your secrets in cloud contexts using #SOPS

#ConLife23

[@jschnatterer @jschnatterer]

Today I had the honor of having @NicholasDille live-tweeting my talk on GitOps patterns on #ConLife23 🤩

[Nicholas Dille @nicholasdille.bsky.social @NicholasDille]

Next up (for me) is Mr. GitOps @jschnatterer

[@jschnatterer @jschnatterer]

. @LeanderReimer pointing out "brown" electricity in Germany at @ConLifecycle #ConLife23

[@jschnatterer @jschnatterer]

Wir suchen Themen von neuen und altbekannten Gesichtern für die Konferenz der deutschsprachigen GitOps-Community 👇

[@jschnatterer @jschnatterer]

Created a downstream @PlantUML "distro" capable of creating PDFs:

docker run --rm -u $(id -u) \
-v /your-folder:/data \
https://t.co/PhAiZsWgXE \
-tpdf your.puml

https://t.co/0KI3h6jaHv

[Forrest Brazeal @forrestbrazeal]

Been noticing some discourse lately about why cloud is overrated. Maybe it is. But there's more to the story.

I wrote this to help me think through things, and if Elon wasn't the way he is you'd be able to tell it was a link called "Wait, is Cloud Bad?" https://t.co/7Fz4RNtOcM