From 64205a79fdc18850d20bbbe4040d587976c7c3d1 Mon Sep 17 00:00:00 2001 From: Ryan Yin Date: Sun, 18 Feb 2024 23:05:31 +0800 Subject: [PATCH] feat: add pulumi related tools --- home/base/desktop/cloud/default.nix | 12 +++++++++++- pulumi/k8s/README.md | 6 ++---- 2 files changed, 13 insertions(+), 5 deletions(-) diff --git a/home/base/desktop/cloud/default.nix b/home/base/desktop/cloud/default.nix index ad6aa7db..402a8467 100644 --- a/home/base/desktop/cloud/default.nix +++ b/home/base/desktop/cloud/default.nix @@ -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 diff --git a/pulumi/k8s/README.md b/pulumi/k8s/README.md index f20b6cf1..c432358d 100644 --- a/pulumi/k8s/README.md +++ b/pulumi/k8s/README.md @@ -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.