Viewing profile — pst

Cool project. Love the clean look.

I've been building a frontend with Go, Templ and Datastar for a few months now. I really like the @actions and how the page is updated with the response. I'm on the fence about sig…

This is awesome. Having a single state for all resources in an environment is critical for keeping all the moving pieces in check and a core design aspect of Kubestack. But the gro…

A lot of work that apparently is not valued enough to justify paying for.

You're not wrong. They add miniscule value. But what does that say about the people using these images who are now struggling to replace them?

Everything under internal did discourage me from trying templUI too. What's the reason for it?

I'm working on an application and use Fiber, Templ and Datastar to keep my frontend in Go, like my backend. I'm overall quite happy with this approach. But Datastar tries to do bot…

But is the icon going to be a syringe, a pill or a tombstone?

Here's the problem, whenever I get onboarded to a new team, it's an endless stream or asking someone to be added to this other GHE repository, get access to a specific Jira board o…

We've got some overlap on the stack part. But I am more focused on the infra side of platform engineering (including bootstrapping clusters), seems for you it's more app dependenci…

Giving teams more insights into their apps at runtime without requiring changes to the apps is as close as one gets to a superpower.

It's funny, as someone proposing frameworks make sense in IaC (Terraform in my case), how the framework/no-framework topic apparently never gets old.

But if you create a configmap to store that label isn't that state? It may be more lightweight than what Terraform or Helm store, but it's still state.

Yes, conditionals and loops in TF are limited and have various annoying and surprising edge cases. But if something is hard to do with the Terraform DSL it's usually a good idea to…

Flux, IIRC, uses labels or annotations to do purging. Helm I'd argue falls into the state category with the secrets if uses to track releases. I do everything with Terraform so I'm…

It's not trivial to get the labels correct to avoid collateral deletions. Also, while it makes sense, I and many teams I consulted with found it rather unintuitive that apply --pur…

Keeping the tombstones around in the configuration I have to maintain instead of the state the tool maintains for me also increases the effort for me though. So either I have the e…

Yes, but setting up and handling edge cases of Terraform state causes the effort. Once you have it, storing just IDs or more doesn't make a difference anymore.

This doesn't work unless your infrastructure is entirely static. As soon as you have active control loops like e.g. an autoscaler it will create resources that you don't know about…

The delete this approach is imperative though. If you aim to be declarative you need a way for the tool to be able to determine actions necessary to go from current to new desired …

I maintain a Terraform provider for Kubernetes. And one of the main reasons for that is because the Terraform state ensures purging of deleted resources. Something that kubectl is …

It's a little unfortunate, the canonical URL was picked up. While yes, this was originally posted on thenewstack.io I updated it to the latest versions of the providers and modules…