Even when you're writing your app, you can write a line,

pulumi up

, write a 2nd line,

pulumi up

and see if it did what you want, etc etc

It's actually an amazing platform for iterative development

Yeah, so, if you really do have two separate setups, a k8s setup, and a Docker-based setup, you'd write two separate Pulumi apps

How do devs usually do local development with k8s stacks?

If you have the $$, I'd instead make a super cut-down version of your k8s setup that spins the absolute minimum of nodes and have every dev create their own

That's a Good Question, I haven't done k8s stuff yet tbh, I see that as a pretty big problem tbh, having development and production being so different

Huh. Yeah, I am in a bit over my head here haha. Unfortunately I have a bit of a fire under my ass so to speak, because I have no other option than figure this out myself and I have perhaps a week or two more to do it 😅

Well thank you for taking the time to answer me, really appreciate you ❤️

I will go back to my docs reading and pound my head against things until I figure it out I suppose lmao

np!

@ambitious-ram-5811 the new “Pulumi watch” stuff is great for iterative development too!

I am very confused, I am trying to put a deployment in a special namespace I created. But the Yaml Pulumi generates points to "default" even though I specify a different namespace.

morning all. ive got a k8s cluster being provisioned and it all works very nicely - i'm using pulumi in typescript and using the digitalocean provider. the only problem ive got is with regards to refreshing the kubeconfig. when i first build the cluster, it generates a kubeconfig which i then set to a k8s provider so i can use it internally. the problem is that the kubeconfig that DO creates expires after 7 days. and because pulumi doesnt know this, it never calls DO to regenerate the token. this is what im doing so far:

const k8s = new digitalocean.KubernetesCluster('Configure k8s', stackConfig.k8s);

const k8sConfig = k8s.kubeConfigs[0].rawConfig;

const k8sProvider = new kubernetes.Provider('Get k8s provider', {
  kubeconfig: k8sConfig,
});

the

k8sProvider

then is set to

provider

options any time i make an additional k8s call, eg

const helmServiceAccount = new kubernetes.core.v1.ServiceAccount(
  'Helm RBAC service account',
  {
    apiVersion: 'v1',
    kind: 'ServiceAccount',
    metadata: {
      name: 'tiller',
      namespace: 'kube-system',
    },
  },
  {
    provider: k8sProvider,
  },
);

as i said, this all works fine for the first 7 days then breaks because the kubeconfig has expired within digitalocean

aaaah, ive found it. it's

pulumi update

- id been playing around with

pulumi refresh

but doesnt work for <reasons> https://github.com/pulumi/pulumi/issues/2710

I’ve tried using

apply

but can’t figure out what to do with it.

What’s the correct way to use

requireSecret

as an argument to a cloud spec? I see that in https://github.com/pulumi/examples/blob/fdf37ddecedb10dcdfa77362f8ece49c52011caa/aws-stackreference-architecture/database/src/index.ts#L30 nothing special is going on but when I follow that pattern like:

const config = new Config();
const dbPassword = config.requireSecret('dbPassword');

// stuff....

const postgresUser = new gcp.sql.User('master', {
  name: dbUser,
  password: dbPassword, // this line errors out. I've also tried dbPassword.get()
  instance: postgresDB.name,
  project: project
});

I get the following error:

index.ts(187,3): error TS2322: Type 'Output<string>' is not assignable to type 'string | Promise<string> | OutputInstance<string> | undefined'.
      Type 'Output<string>' is not assignable to type 'OutputInstance<string>'.
        Types of property 'apply' are incompatible.
          Type '{ <U>(func: (t: string) => Promise<U>): import("/Users/paymahn/qwil/[secret]/pulumi/infra/node_modules/@pulumi/pulumi/output").Output<U>; <U>(func: (t: string) => import("/Users/paymahn/qwil/[secret]/pulumi/infra/node_modules/@pulumi/pulumi/output").OutputInstance<U>): import("/Users/paymahn/qwil/[secret]/pulumi/infra/nod...' is not assignable to type '{ <U>(func: (t: string) => Promise<U>): import("/Users/paymahn/qwil/[secret]/pulumi/node_modules/@pulumi/pulumi/output").Output<U>; <U>(func: (t: string) => import("/Users/paymahn/qwil/[secret]/pulumi/node_modules/@pulumi/pulumi/output").OutputInstance<U>): import("/Users/paymahn/qwil/[secret]/pulumi/node_modules/@pulumi/...'.
            Type 'import("/Users/paymahn/qwil/[secret]/pulumi/infra/node_modules/@pulumi/pulumi/output").Output<any>' is not assignable to type 'import("/Users/paymahn/qwil/[secret]/pulumi/node_modules/@pulumi/pulumi/output").Output<any>'.
              Type 'OutputInstance<any>' is not assignable to type 'Output<any>'.
                Type 'OutputInstance<any>' is not assignable to type 'OutputInstance<any> & LiftedObject<any, string>'.
                  Type 'import("/Users/paymahn/qwil/[secret]/pulumi/infra/node_modules/@pulumi/pulumi/output").OutputInstance<any>' is not assignable to type 'import("/Users/paymahn/qwil/[secret]/pulumi/node_modules/@pulumi/pulumi/output").OutputInstance<any>'.
                    Types of property 'apply' are incompatible.
                      Type '{ <U>(func: (t: any) => Promise<U>): import("/Users/paymahn/qwil/[secret]/pulumi/infra/node_modules/@pulumi/pulumi/output").Output<U>; <U>(func: (t: any) => import("/Users/paymahn/qwil/[secret]/pulumi/infra/node_modules/@pulumi/pulumi/output").OutputInstance<U>): import("/Users/paymahn/qwil/[secret]/pulumi/infra/node_modu...' is not assignable to type '{ <U>(func: (t: any) => Promise<U>): import("/Users/paymahn/qwil/[secret]/pulumi/node_modules/@pulumi/pulumi/output").Output<U>; <U>(func: (t: any) => import("/Users/paymahn/qwil/[secret]/pulumi/node_modules/@pulumi/pulumi/output").OutputInstance<U>): import("/Users/paymahn/qwil/[secret]/pulumi/node_modules/@pulumi/pulumi...'.
                        Type 'import("/Users/paymahn/qwil/[secret]/pulumi/infra/node_modules/@pulumi/pulumi/output").Output<any>' is not assignable to type 'import("/Users/paymahn/qwil/[secret]/pulumi/node_modules/@pulumi/pulumi/output").Output<any>'.
                          Type 'OutputInstance<any>' is not assignable to type 'Output<any>'.
                            Type 'OutputInstance<any>' is not assignable to type 'OutputInstance<any> & LiftedObject<any, string>'.
                              Type 'OutputInstance<any>' is not assignable to type 'LiftedObject<any, string>'.
                                Index signature is missing in type 'OutputInstance<any>'.

I’ve tried calling

.get()

on

dbPassword

but that results in another error of

Error: Cannot call '.get' during update or preview.
    To manipulate the value of this Output, use '.apply' instead.

I’ve declared a docker image like:

const appImage = new docker.Image("ledgerImage", {
    imageName: '<http://us.gcr.io/qwil-build/ledger|us.gcr.io/qwil-build/ledger>',
    build: "../../",
});

When I run

pulumi preview

and look at the output in app.pulumi.com I see the line

Successfully pushed to docker

in the Diagnostic Log view. Where did pulumi push this image? When I visit my companies gcr registry I don’t see any new images - the latest image that was uploaded is from 2 days ago.

Can we run aws cli commands inside pulumi?

Did anybody already use Azure AKS (Kubernetes service) with multiple node pools (aka VMSS)? I’m specifically looking for some hints on how to handle the different pools together with custom networking (vnet, subnet), azure-cni and the Standard SKU load balancer required for the vm scale sets. Thanks for any pointer!

any complex examples with typescript out there? Like classes, interfaces and the like? Just need some advice on how to set it up in an enterprise environment. going beyond the simple index.ts examples ;)

How does Pulumi handle Kubernetes API deprecations these days, e.g.: https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/ We have some

apiVersion: extensions/v1beta1

resources that we want to change to, e.g.

apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>

. My experience with Helm is that it kinda fucks up here, because for e.g.: a deployment named

foo

, we can't tell Helm "don't change anything with this resource, just update Tiller with what the new API version is because k8s allows us to access a deployment via both extensions/v1beta1 and apps/v1". The result is we have to rename everything to

foo-v1

, experiencing some downtime because Helm will tear down the old deployment, stand up the new deployment, and often other stuff is also infected with the name via Helm templating so the service, the ingress, etc all get replaced and/or destroyed and recreated as the new name. Is there a way to make Pulumi just... accept that these resources are now

<http://networking.k8s.io/v1|networking.k8s.io/v1>

or

apps/v1

? That is, no update/replace/etc needed.

Has anyone here seen

AssertionError: Failure: Decoder hit an error

error when trying to

pulumi up

?

I deleted my k8s cluster from the AWS console. Now my Pulumi stack fails with "unable to load schema information from the API server". Is there a way to simply tell Pulumi that the EKS cluster is gone so all of the k8s resources are also gone?

I'm trying to use pulumi with the program in one directory and the stack files in another. e.g.

❯ tree
.
├── program
│   └── index.ts
└── stack
    ├── Pulumi.my-stack.yaml
    └── Pulumi.yaml

is this feasible?

Hello all, Quick question regarding to Azure SQl Server. How could I set "Allow Azure services and resources to access this server" from pulumi when provision the server and how to restrict to particular AzureDevOps instance?

Hrm, I recently added a FargateTaskDefinition into my pulumi project... it works great, but it means now that every time I

pulumi up

it builds the image and pushes it to the container registry, even if there were no changes. This takes a fair bit of time, and requires that I have Docker running even if I'm not actively doing any Docker work. Anyone know of a way to have it only do the docker work if changes were actually made to the docker files?

message has been deleted

Hi All, How could we specify the vCore of SQL Db when creating new database with General Purpose edition? Thanks all 🙂

Is it possible to install the Pulumi CLI via NPM? Maybe something like

yarn add @pulumi/cli

?