other issues but not that one 🙂

Anybody know of any good Typescript support groups? The Pulumi folks have been super helpful and generous with my noob questions but I feel bad taking up their time on things that are TS/JS/Node. If anybody feels like a DM or knows of a good Slack etc please let me know. Thanks!

+1 on @orange-tailor-85423's question/request. I'm in need of a similar resource.

Reposting https://github.com/pulumi/pulumi-awsx/issues/267 in this channel. I’m not sure how to provide a repro, but I’m happy to get into a DM conversation with someone to provide more information

@white-balloon-205 @gentle-diamond-70147 and other mods - can we have a #typescript channel created? We’d love pulumi expert help but also a place for the community to haggle over TS/JS specific issues. I could be wrong but for a number of engineers this might be their first experience with a programming language on a day to day basis

hi 🙂 I'm trying out a bunch of the Pulumi examples (and trying to build my own based on that 😅). When I run

pulumi up

I get the error:

Diagnostics:
  pulumi:providers:docker (default):
    error: no resource plugin 'docker' found in the workspace or on your $PATH

Where can I find the list of supported plugins? I read that I'd need to run

pulumi plugin install ...

but I can't find the right command for the docker plugin

How do I run a fargate task once, built from a pulumi stack, preferably within or close to the pulumi stack script I want to create a task definition for fargate, and run the task once. The purpose is to run a custom build script on a build server using a custom image built in an awsx.ecs.Image. awsx.ecs.FargateTaskDefinition#run() complains that it can't run the task during a preview or a get. This makes sense to me, as it would need to wait until the task was created, including all it's dependencies. I can see several ways to run the task once its created using aws scripts or a enclosing script or <?>. I am interested in getting advice on what the preferred way to execute a fargate task like this would be.

error: Running program '/mnt/e/Development/apps/inside-v-next/ivn-build/ivn-build-stack' failed with an unhandled exception:
    Error: Cannot call '.get' during update or preview.

I'm having a strange issue trying to use express js in a lambda. It's to do with how error handlers are called. The way express distinguishes between an error handler and a non-error handler is by checking the function.length which returns the arity of the function. It seems somewhere between the source code and what's getting deployed something is messing with this as an arity of 0 is logged out. Are there any known issues around this? Could pulumi's serialization be breaking it?

So I'm trying to move a helm chart provisioned using pulumi to a different namespace, the helm chart includes a cluster role binding and it already exists, this is making pulumi fail with this message:

kubernetes:<http://rbac.authorization.k8s.io:ClusterRoleBinding|rbac.authorization.k8s.io:ClusterRoleBinding> (monitoring/kube-state-metrics):
    error: Plan apply failed: <http://clusterrolebindings.rbac.authorization.k8s.io|clusterrolebindings.rbac.authorization.k8s.io> "kube-state-metrics" already exists

Is this a known issue ? If not how do I get over this ? I know I can manually delete the kube-state-metrics binding

I have a google load balancer created via a k8s ingress, is there any way to manage it via pulumi?

@helpful-advantage-49286 If you want to change some configuration on the LB, you'll probably need to have it created by Pulumi (instead of created by Kubernetes). I could be wrong, though, so I'll defer to others. If you're interested in making changes to the ingress object (which is serviced by the LB), then that might be doable, though I suspect you'd still need to have the ingress object created by Pulumi instead of outside Pulumi.

i’d be happy to do that, but how do i do that and end up with it being used properly by k8s?

the ability to import resources is "on its way" last i heard

if you're very brave you can edit your stack file manually by getting the resource IDs / dependencies etc. correct

not that brave 🙂

also, reproducability is super key for us for compliance purposes 🙂

@helpful-advantage-49286 To have the ingress controller and associated objects created by Pulumi, you'd need to use the Kubernetes plugin/package (looks like it's available for JS/TS and Python). Then you'd write your code to create your objects, and

pulumi up

would instantiate the objects on the Kubernetes cluster(s).

yeah, so thats what I do

See https://pulumi.io/reference/pkg/nodejs/@pulumi/kubernetes/index.html for the JS/TS information.

that causes a GLBC instance to be created

So let me take a step back here---can you elaborate a bit on exactly what you'd like to achieve?

I am trying to make some changes to the config of the GLBC instance created by k8s

Generally, you'd make those changes through Kubernetes, usually by changing the properties of the Service object that is responsible for creating the LB through the cloud provider (GCP, in this case).

How familiar are you with K8s? (I don't want to assume the wrong level of knowledge/experience.)

fairly

the issue is the stuff i want to change isn’t exposed by k8s

(i want to have the LB just proxy traffic to another service, basically SNI-based https->http for a help site that is hosted somewhere else)

I am about to just push up a tiny nginx container that does that proxying and point the backend at that, but its not optimal considering GLB can do it directly.

Let me see if I understand the situation. You have an ingress controller on a K8s cluster that is exposed via a Service of type LoadBalancer (and thus creates a GCP LB). You want the ingress controller to direct traffic to a site that is external to the Kubernetes cluster, is that correct?