Thanks!

error: Running program '/Users/harrison/code/linio/infrastructure/applications/cert-manager' failed with an unhandled exception:
    TypeError: Cannot read property 'concat' of undefined
        at /Users/harrison/code/linio/infrastructure/node_modules/@pulumi/pulumi/runtime/resource.js:359:29
        at Generator.next (<anonymous>)
        at fulfilled (/Users/harrison/code/linio/infrastructure/node_modules/@pulumi/pulumi/runtime/resource.js:18:58)

    TypeError: Cannot read property 'concat' of undefined
        at /Users/harrison/code/linio/infrastructure/node_modules/@pulumi/pulumi/runtime/resource.js:359:29
        at Generator.next (<anonymous>)
        at fulfilled (/Users/harrison/code/linio/infrastructure/node_modules/@pulumi/pulumi/runtime/resource.js:18:58)

  kubernetes:helm.sh:Chart (cert-manager):
    [Can't preview] all chart values must be known ahead of time to generate an accurate preview.

Is this a known issue?

A heads up for folks dealing with EKS and the aws-auth configmap

we’ve been testing the AWS SSO product the last few days and passing in the arn of one of these roles in the format:

arn:aws:iam::11111111111111:role/aws-reserved/sso.amazonaws.com/us-west-2/AWSReservedSSO_PowerUserAccess_bf7fc98648d51168

does not work

or I should say, passing in the short name of

AWSReservedSSO_PowerUserAccess_bf7fc98648d51168

results in the full arn in the configmap which does not work

after the pulumi run I need to manually fix the configMap

Found the related fix here: https://aws.amazon.com/blogs/opensource/integrating-ldap-ad-users-kubernetes-rbac-aws-iam-authenticator-project/ (Nishi FTW!)

it led us to check the configMap and sure enough found the issue:

For the rolearn be sure to remove the /aws-reserved/sso.amazonaws.com/ from the rolearn url, otherwise the arn will not be able to authorize as a valid user.

I got a timeout trying to update an eks cluster from k8s 1.13 to 1.14:

Dev-EksPulumi-eksCluster (eks:index:Cluster$aws:eks/cluster:Cluster)
error: Plan apply failed: 1 error occurred:
	* updating urn:pulumi:dev::k8s-infra::eks:index:Cluster$aws:eks/cluster:Cluster::Dev-EksPulumi-eksCluster: error waiting for EKS Cluster (Dev-EksPulumi-eksCluster-d16ec52) version update (3222e27e-b126-4546-9e37-d6b251e4a025): timeout while waiting for state to become 'Cancelled, Failed, Successful' (last state: 'InProgress', timeout: 20m0s)

Is this configurable somewhere?

Hi, I like the concept, but I’d like to know what the web app is for? Is the pulumi script actually creating stuff when I run it or is is pulumi’s backend that does it? If so, why was it built like that?

Hello, I didn't see an answer but it looks like debug-ability of Pulumi programs is still not possible yet. Is that true? (based on this issue: https://github.com/pulumi/pulumi/issues/1372)

I have a binary file stored locally that I need to load into a volume and be accessible from a container. Using kubernetes, we can include it as a secret and use --from-file. Is there an equivalent way to do this with Pulumi?

can someone help me with the

ignoreChanges

path - if there is documentation on this somewhere I’m having trouble finding it, this is the best I’ve found so far: https://github.com/pulumi/pulumi/pull/3005/files/8a4b20b05ec9c4ceb1535d90ddb350319655a8c3#diff-7bb15b0066584f354ca6a55865d99ffeR29

i just can't seem to get the nginx ingress helm chart installed any more. i always end up with

error: Plan apply failed: 2 errors occurred:
	* 'nginxingresscontroller-nginx-ingress-controller' timed out waiting to be Ready
	* Minimum number of live Pods was not attained


error: Plan apply failed: 2 errors occurred:
	* 'nginxingresscontroller-nginx-ingress-default-backend' timed out waiting to be Ready
	* Minimum number of live Pods was not attained

We are trying to upgrade our EKS nodes. https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/eks/#ClusterNodeGroupOptions In

ClusterNodeGroupOptions

when we specify

version: '1.13.10',

from

1.13

the

preview

does not recognize it as a change. What could I be missing? Thanks

I'm very impressed with the amount of customization already in place for the aws vpc cni. I've had to update this as part of infra deploy in the past and it's much appreciated. Similarly, I've updated the CoreDNS and KubeProxy as part of infra deploy, since Amazon does not update this automatically when you update a cluster. https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html @white-balloon-205 do you think this is something Pulumi could / should support too?

hello peeps! i was curious if anyone knows how to handle multiple authorization types for

GraphQLApiArgs

as described here: https://aws.amazon.com/blogs/mobile/using-multiple-authorization-types-with-aws-appsync-graphql-apis/

if an output (i.e. an

export

) is

undefined

, does that make it not appear in the list of outputs? i'm trying to track down an error where sometimes one of my deployments is missing an image. i'm exporting a hash of

{app1: image1, app2: image2}

, and i see in the output i only have

{app1: image1}

, when i would have expected

{app1: image1, app2: undefined}

if the variable was undefined.

Hi i noticed that the pulumi docker image, does not have helm installed. If we were to use the library

k8s.helm.v2.Chart

Do we need to install helm above the pulumi image? What do you recommend?

is

.metadata.apply(m => m.name)

still a thing? i thought this went away for some reason, but i just saw an error related to calling a

k8sservice.metadata.name

directly. maybe because im putting it into a string interpolation?

that was totally it, pulumi.interpolate

is anyone else having trouble with https://app.pulumi.com/ ? Getting HTTP 500's and missing organisations

The docs (https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/gcp/dns/#RecordSet) show this code with

accessConfig.0.natIp

. Is this valid TS?

const frontendRecordSet = new gcp.dns.RecordSet("frontend", {
    managedZone: prod.name,
    rrdatas: [frontendInstance.networkInterfaces[0].accessConfig.0.natIp],
    ttl: 300,
    type: "A",
});

is there any reasonably simple way for me to test this: https://github.com/pulumi/pulumi-azure/pull/361 to see if it also fixes https://github.com/pulumi/pulumi-azure/issues/359

alright so after working with Pulumi programs for a while on my local, it’s time to put everything in my CI.. oh wait, yaml files.. I got so spoiled by not working with disgusting yaml files that writting my CI sequence in it feels weird and unefficient… any thoughts? I’d love to have CI/CD as code

can I execute cmd commands in a pulumi program? I would like to

git clone

a helm chart and run it after

is it possible to have a Pulumi.yaml in a parent folder and have the Pulumi.<stack-name>.yaml in sub directories? right now I just copy my Pulumi.yaml over

Any tips or best practices for Kubernetes namespaces vs Pulumi’s stacks? I’m reading the docs right now, not sure if I saw something about it

how is admin status in Pulumi orgs determined if we’re using Github integration

troubleshooting a new issue that cropped up in Azure VM land.. i’m pretty sure it’s an azure issue, but not even sure where to start