6 ms·

Thank you! I've seen that and I don't fully like it. I am not interested in deploying the configuration. I believe that generating configuration, versioning it,

Thank you! I've seen that and I don't fully like it. I am not interested in deploying the configuration. I believe that generating configuration, versioning it, baking it, should be a totally separate process to deploying, rolling out, reverting etc That's why IMO we should separate those. (:

reilly3000 7y ago
We are writing Pulumi in node (far more mature then their Go offering, but that has been recently improved) and version our releases into private NPM packages. That isn’t strictly necessary, as every update Pulumi pushes gets versioned internally along with associated code changes, and is always accessible in the stack’s history. If you’re a K8s dev, they recently announced the ability to output Helm3 files rather than deploy directly.
- witcher 7y ago
  I am k8s dev, but also I think Helm is antipattern. Still thanks for sharing your experience, who knows, maybe worth to look again on Pulumi. (:
  - reilly3000 7y ago
    I misspoke - it generates straight yaml not helm https://www.pulumi.com/blog/kubernetes-yaml-generation/ https://www.pulumi.com/blog/kubernetes-yaml-generation/
    - witcher 7y ago
      Nice!