Happy Xmas to every one :)

It’s a question of who your biggest audience is. Have you surveyed new Pulumi adoptees on what languages they already know?

I wasn't involved in that decision at all, but FWIW, TypeScript has a strong type system and is concise and expressive at the same time. Combined with the largest ecosystem of libraries and tools of Node.js, I think it's a solid choice.

Probably, TypeScript makes more sense for my background (full stack dev) than for DevOps/platform teams.

Hi, We are using statefulset(https://github.com/elastic/helm-charts/blob/7.5.0/elasticsearch/templates/statefulset.yaml) and spinning up eks through Pulumi code. It is creating aws ebs volumes and everything is working fine. Scenario is that, When the perform pulumi destroy (bringing down the cluster) and bring it up again(pulumi up ), statefulset is creating new volumes instead of reusing existing ones. We are in testing phase where we don't want to keep 5 node cluster running all the time and at the same time, we don't want to recreate the data all the time. So, we would like to shutdown and start when ever needed. Is there is any approach you could recommend to re-use existing ebs volumes. Also, in real scenarios, Eks can go down for n number of reasons and it is very important for us to address reusing volumes. Please advise.

HELP! It seems that changing awsrdsSubnetGroup description (!!!) is causing an awsrdsClusterInstace replacement. This is insane! We tried different pulumi/aws versions: 1.7.0 - 1.14.0 - happens on all of them. Note that in pulumi/aws 1.8.0 there is a change to subnetgroup description so we are currently stuck on 1.7.0 due to this breaking change.

Question about stacks - what’s the best way to migrate a stack from my personal account (under my profile) to an organization (so that others can also manage)?

I'm trying to use Pulumi to deploy an instance of Hashicorp Vault in Kubernetes, then connect to it using the pulumi-vault provider and provision a bunch of resources in it. Is there a good way to handle the chicken-and-egg problem this creates for preview? Pulumi can't preview the changes to be made in Vault because the instance of Vault that it would connect to to preview those changes has not been created yet, and won't be until apply time.

Does anyone know how to setup some logging from a containers stdout & stdin using EKS & Fargate and Pulumi? I want to use Prometheus and Loki but not sure how to setup it up with pulumi. I think something missing from Pulumi docs for getting a production ready rollup is something related to capturing metrics and logging from all containers, preferably without changing our app images. We use stdout and stdin.

Posting here rather than #python because I don’t think it’s specific to Python. I have Pulumi installed manually in ~/.pulumi/bin. I have a virtualenv set up and pulumi Python package installed with pip. I start

python3

and try to do the following at the interactive prompt:

>>> import pulumi
>>> config = pulumi.Config()

and I get “Program run without the Pulumi engine available; re-run using the

pulumi

CLI” The pulumi binary is in PATH, I checked with

print(os.environ["PATH"])

What else does it need?

In general what I can do in Pulumi that Terraform cannot do?

@elegant-twilight-2745 you probably want this page: https://www.pulumi.com/docs/intro/vs/

With pulumi then I don’t need Boto3? Could someone explain thanks

@here looking for help with a cloudfront deployment problem (see #aws)

Upgrading to

@pulumi/pulumi=1.8.1

with typescript has introduced this error for me:

stacks/cluster/api.ts(85,8): error TS2345: Argument of type '{ parent: this; }' is not assignable to parameter of type 'CustomResourceOptions'.
      Types of property 'parent' are incompatible.
        Type 'this' is not assignable to type 'Resource | undefined'.
          Type 'this' is not assignable to type 'Resource'

where

this

is a

class API extends pulumi.ComponentResource

Has anyone noticed npm update does not work after updating to the latest version?

Is helm 3 fully supported? I’m experimenting with gloo and so I have a pulumi file like this:

import * as k8s from '@pulumi/kubernetes'

new k8s.helm.v2.Chart('gloo', {
  chart: 'gloo/gloo',
})

Pulumi fails with:

Error: Command failed: helm fetch gloo/gloo --untar --destination /tmp/tmp-12397xMcptBYcaXX7

In gloo docs, it mentions this bug in version 2: https://docs.solo.io/gloo/latest/installation/gateway/kubernetes/#installing-on-kubernetes-with-helm However, I have helm v3 installed in my path: $ helm version version.BuildInfo{Version:“v3.0.2”, GitCommit:“19e47ee3283ae98139d98460de796c1be1e3975f”, GitTreeState:“clean”, GoVersion:“go1.13.5"} Looking through pulumi-kubernetes I was able to find: https://github.com/pulumi/pulumi-kubernetes/pull/882 (Merged)

@rhythmic-hair-33677 I don’t think so, since Helm3 is fully client side.

@rhythmic-hair-33677 What we do is translate the helm charts to regular k8 manifest files and apply those instead.

I genuinely dislike Helm with a passion.

@flat-insurance-25294 So you are saying helm 3 is not supported? It seemed to work fine with other charts but not on this particular one.

No, I am saying Helm3 is very different from Helm2 Could be this Chart isn’t supported on Helm3 then?

Well helm install is supported by the chart. I’ll check if helm template works.

Hmm, I need to add the ALB (ingress) address to route53. One approach was to reference the ALB using

static get()

but there is no way of knowing the name of the ALB created. Another approach is to print the ingress using kubectl and use the address with https://github.com/pulumi/pulumi-query-kubernetes But the question is, is it lazy? As if will it wait until the cluster has been setup?

I have a helm chart with a

"<http://helm.sh/hook|helm.sh/hook>": crd-install  annotation

. Pulumi just skips that resource entirely. How do you install CRDs with pulumi and helm v3? It seems to entirely ignore what is in the crds directory. Pulumi logs this several times: manifest_sorter.go175 info: skipping unknown hook: “crd-install” I’m not seeing that file in pulumi-kubernetes, so I assume it is coming directly from helm template.

Hi everybody, I am from Taiwan. My English is bad, but I present my question clear asap. I am a .Net developer. Where can I learn pulumi with .net or doc?

Is there any way to enable detailed monitoring on an EKS NodeGroup?

is there a way to just run the equivalent of

pulumi stack ls --json

from the API? I need to enumerate existing stacks of a certain type in order to decide some details about the next stack

piping in that command from my script seems a bit... weird..

I was thinking to do some testing with Pulumi and would like to know what is "recommended" language or is there any?