mirror of
https://github.com/ryan4yin/nix-config.git
synced 2026-03-18 15:34:13 +01:00
feat: add pulumi related tools
This commit is contained in:
@@ -2,9 +2,19 @@
|
||||
home.packages = with pkgs;
|
||||
[
|
||||
# general tools
|
||||
packer # machine image builder
|
||||
|
||||
# infrastructure as code
|
||||
pulumi
|
||||
pulumictl
|
||||
packer # machine image builder
|
||||
tf2pulumi
|
||||
crd2pulumi
|
||||
pulumiPackages.pulumi-random
|
||||
pulumiPackages.pulumi-command
|
||||
pulumiPackages.pulumi-aws-native
|
||||
pulumiPackages.pulumi-language-go
|
||||
pulumiPackages.pulumi-language-python
|
||||
pulumiPackages.pulumi-language-nodejs
|
||||
|
||||
# aws
|
||||
awscli2
|
||||
|
||||
@@ -3,11 +3,9 @@
|
||||
|
||||
## Why Pulumi for Kubernetes?
|
||||
|
||||
1. Deploying Helm charts declaratively.
|
||||
- Helm CLI supports only imperative commands, you need to add a repository, update the repository,
|
||||
and install the chart with a single command,
|
||||
1. 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.
|
||||
- Pulumi can deploy Helm charts declaratively, you can manage the lifecycle of the Helm chart easily.
|
||||
1. Deal with secrets in a secure way.
|
||||
1. Deploying Kubernetes resources in a unified way, instead of running a bunch of commands like `kubectl apply`, `helm install`, `kustomize`, etc.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user