pst

6 ms·

1.
by pst 5mo ago
Cool project. Love the clean look.
2.
by pst 1y ago
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 signals though. They are fine for simple things like
3.
by pst 1y ago
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 growing state files quickly become a bottleneck. I'm defin
4.
by pst 1y ago
A lot of work that apparently is not valued enough to justify paying for.
5.
by pst 1y ago
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?
6.
by pst 1y ago
Everything under internal did discourage me from trying templUI too. What's the reason for it?
7.
by pst 1y ago
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 both, AlpineJS stuff like show/hide dropdow opti
8.
by pst 3y ago
But is the icon going to be a syringe, a pill or a tombstone?
9.
Ask HN: How to ensure correct access across all SaaS services
1 points by pst 3y ago|0 comments
10.
by pst 3y ago
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 dependencies. Check https://www.kubestack.com an
11.
Terraform Platform Engineering Framework(kubestack.com)
3 points by pst 3y ago|0 comments
12.
by pst 4y ago
Giving teams more insights into their apps at runtime without requiring changes to the apps is as close as one gets to a superpower.
13.
by pst 4y ago
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.
14.
by pst 4y ago
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.
15.
by pst 4y ago
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 reconsider if it is really something that one should b
16.
by pst 4y ago
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 not super familiar with either of them. But teams
17.
by pst 4y ago
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 --purge with a label selector will also only update resource
18.
by pst 4y ago
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 effort of setting up the remote state and handling some edge
19.
by pst 4y ago
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.
20.
by pst 4y ago
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 and would then delete.
21.
by pst 4y ago
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 configuration. You need to store previous applied config som
22.
by pst 4y ago
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 not capable of. The lastAppliedConfig annotation does not he
23.
by pst 4y ago
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 and fixed the code examples, which I could not on The
24.
A Better Way to Provision Kubernetes Resources Using Terraform(thenewstack.io)
2 points by pst 4y ago|1 comments
25.
GitHub: Stolen OAuth User Tokens (Heroku, Travis-CI)(twitter.com)
14 points by pst 4y ago|0 comments
26.
by pst 5y ago
Thanks for the kind words. I'm building Kubestack because I believe strongly that frameworks make sense for IaC too and that platform teams need a better DX if they are supposed to deliver a better DX to app teams. I'm currently h
27.
by pst 5y ago
I'm following a similar approach with Kubestack. Although for a much smaller use-case, being exclusively focused on building Kubernetes platforms using Terraform. Your scope sounds more like Gruntwork. How would you say you differentia
28.
by pst 5y ago
Rancher doesn’t generate Terraform code. It further doesn’t have a platform of multiple clusters as it’s core concept. And as a result it can’t provide the same preview, validate and promote GitOps workflow. More details here: https:/
29.
by pst 5y ago
Kubestack Cloud is a low-code UI to define Kubernetes platforms and export them to production grade Terraform. Architecting a K8s platform is time-consuming and difficult. It gets easier if you've done it before, of course, but then it
30.
Show HN: Low-code UI to design a K8s platform and export Terraform code(kubestack.com)
6 points by pst 5y ago|3 comments

More ›