mirror of
https://github.com/ryan4yin/nix-config.git
synced 2026-04-21 00:11:26 +02:00
1ead059695
Bumps [github.com/cloudflare/circl](https://github.com/cloudflare/circl) from 1.3.3 to 1.3.7. - [Release notes](https://github.com/cloudflare/circl/releases) - [Commits](https://github.com/cloudflare/circl/compare/v1.3.3...v1.3.7) --- updated-dependencies: - dependency-name: github.com/cloudflare/circl dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Pulumi - Infrastructure as Code
WIP, not working yet.
My infrastructure is managed by Pulumi & NixOS.
Why Pulumi for Kubernetes?
- Deploying Helm charts & yaml files in the right order, in a declarative way.
- Helm CLI supports only imperative commands, you need to run a bunch of commands like
helm repo add,helm repo update,helm install,helm upgrade, etc. it's really hard to manage the lifecycle of the Helm chart in this way.
- Helm CLI supports only imperative commands, you need to run a bunch of commands like
- Deal with secrets in a secure way.
- Deploying Kubernetes resources in a unified way, instead of running a bunch of commands like
kubectl apply,helm install,kustomize, etc.
Why not ArgoCD or FluxCD?
ArgoCD & FluxCD support only Kubernetes, and it's too heavy for my use case.
Pulumi supports not only Kubernetes but also other cloud providers like Proxmox, Libvirt, AWS, Azure, GCP, etc. It's a unified way to manage the lifecycle of all my infrastructure resources.