pulumi-community #general

Docs

Join the conversation Join Slack

Channels

general

famous-twilight-87777

09/21/2020, 10:41 AM

I have a strange error here:

famous-twilight-87777

09/21/2020, 10:41 AM

const assoc_bastion_ip = new os.networking.FloatingIpAssociate("associate_bastion_fip", {
    floatingIp: bastion_ip,
    portId: bastion.networks[0].port
});

famous-twilight-87777

09/21/2020, 10:42 AM

where bastion_ip is a const string the error reported is

famous-twilight-87777

09/21/2020, 10:42 AM

Diagnostics:
  openstack:networking:FloatingIpAssociate (associate_bastion_fip):
    error: openstack:networking/floatingIpAssociate:FloatingIpAssociate resource 'associate_bastion_fip' has a problem: Missing required property 'portId'

elegant-island-39916

09/21/2020, 11:00 AM

hi, im trying to deploy a helm chart to eks v1.17 and im running into apiversion issues (latest

pulumi_kubernetes

) pulumi for k8s dashboard helm chart:

k8s_dash = helm.Chart(
    "kubernetes-dashboard",
    config=helm.ChartOpts(
        repo="stable",
        chart="kubernetes-dashboard",
        version="1.5.2",
        namespace="kube-system",
    ),
    opts=pulumi.ResourceOptions(
        providers={"kubernetes": cluster_provider}
    ),
)

output:

Diagnostics:
  kubernetes:<http://rbac.authorization.k8s.io:Role|rbac.authorization.k8s.io:Role> (kube-system/kubernetes-dashboard):
    warning: <http://rbac.authorization.k8s.io/v1beta1/Role|rbac.authorization.k8s.io/v1beta1/Role> is deprecated by <http://rbac.authorization.k8s.io/v1/Role|rbac.authorization.k8s.io/v1/Role> and not supported by Kubernetes v1.22+ clusters.
 
  kubernetes:<http://rbac.authorization.k8s.io:RoleBinding|rbac.authorization.k8s.io:RoleBinding> (kube-system/kubernetes-dashboard):
    warning: <http://rbac.authorization.k8s.io/v1beta1/RoleBinding|rbac.authorization.k8s.io/v1beta1/RoleBinding> is deprecated by <http://rbac.authorization.k8s.io/v1/RoleBinding|rbac.authorization.k8s.io/v1/RoleBinding> and not supported by Kubernetes v1.22+ clusters.
 
  kubernetes:extensions:Deployment (kube-system/kubernetes-dashboard):
    error: apiVersion "extensions/v1beta1/Deployment" was removed in Kubernetes 1.16. Use "apps/v1/Deployment" instead.
    See <https://git.k8s.io/kubernetes/CHANGELOG/CHANGELOG-1.16.md#deprecations-and-removals> for more information.

where can i adjust apiversion for pulumi to avoid this issue?

adamant-byte-68515

09/21/2020, 12:18 PM

Hi, We are facing an issue when creating encrypted neptune cluster via pulumi. This is the link(https://github.com/pulumi/pulumi/issues/5428) to the issue. Someone please have a look at this.

➕ 3

👍 1

red-area-47037

09/21/2020, 12:33 PM

We are currently working on Pulumi Scripts to create an environment to run our software. This would be in Pulumi terminology a project. In order to define different environments Pulumi allows you to create different stacks. By default a the stack configuration is put into a Pulumi.<stack-name>.yaml file inside of the Project directory. We were thinking of keeping the project definition and the stack definition in different directories / repos. Is there any easy way to point Pulumi to a stack configuration in a different directory or another way to achieve the same…

future-morning-96441

09/21/2020, 1:43 PM

Hi, I'm hitting a wall of

fatal error: heap out of memory

for several days now (using pulumi with node), Are there any known antipatterns in Pulumi, which can cause this? It tried to use more verbose logging and tracing but couldn't find any hint about what is causing this. (see error message in my next message) I vaguely guess this could be either during stack-output-serialization or serializing and packaging lambda-functions but I sadly don't have any hard evidence to pinpoint the location. Does anyone have some advice on how to proceed analyzing this error or what can cause this?

clever-byte-21551

09/21/2020, 6:02 PM

I’m trying to use

PULUMI_CONFIG_PASSPHRASE_FILE

and I get this error:

FATA[0729] Failed to deploy                              error="failed to update infra stack: failed to update stack: failed to get stack outputs: code: 255\n, stdout: \n, stderr: error: decrypting secret value: failed to decrypt: incorrect passphrase, please set PULUMI_CONFIG_PASSPHRASE to the correct passphrase\n\n: failed to select stack: exit status 255"

Any idea why? @broad-dog-22463

clever-plumber-29709

09/21/2020, 10:01 PM

I'm trying to migrate a pulumi stack from a s3 backed to the pulumi, but i'm getting an error:

$ pulumi stack import --file github.singular.checkpoint.json
error: could not deserialize deployment: constructing secrets manager of type "cloud": secrets (code=Unknown): NoCredentialProviders: no valid providers in chain. Deprecated.
        For verbose messaging see aws.Config.CredentialsChainVerboseErrors

quiet-helicopter-40480

09/22/2020, 1:20 AM

Hi, I’m using the C# provider and trying to use .Apply to update appsettings on an AppService, but it after the Up completes and I inspect the AppService configuration, none of the settings are present. I’ve successfully used Apply for firewall rules and connection strings, what did I miss here?

clever-plumber-29709

09/22/2020, 1:55 AM

So I'm implementing a new project on pulumi, will be a kind of a big infra. I was planing on using Python which is what i know and use at least for simple scripts (nothing too fancy, so wouldn't either say i'm an expert in it.) But given all the abstractions that awsx provides, i'm temped to use TS in order to use awsx. I would use the vpn, ecs on fargate, ecr, api gateway, and maybe more of this modules provided by awsx. But my experience in TS is 0, and my experience in javascript is also not great, so not much to leverage from that. I have never work on big JS o TS projects. So i'm really torn in between leveraging my knowledge in python but creating all infra from 0 or leveraging the awsx great resources but starting with the language and the project from 0 Any ideas, comments, feedback, experiences and advices would be greatly appreciated.

handsome-zebra-11018

09/22/2020, 3:59 AM

Looks default timeout for

pulumi up

command is 10 mins? Can we reduce it via some config? When I kill pulumi up and start new one.. it complains old one is still running..

famous-twilight-87777

09/22/2020, 5:34 AM

Is there a facility in pulumi to use a template file and inject values into the string?

clever-byte-21551

09/22/2020, 5:36 AM

Is there a way to get an existing object OR create it? does it makes sense to do something like: 1. Try to get the resource by a specific name / arn 2. If I got a not found error if the previous statement was successful I’ll add an import statement to the NewResource statement, otherwise I won’t. Does that makes sense?

famous-twilight-87777

09/22/2020, 6:00 AM

userData supports base64 encoding and gzip with terraform however it seems to be just a plain string with pulumi

famous-twilight-87777

09/22/2020, 6:00 AM

https://www.pulumi.com/docs/reference/pkg/openstack/compute/instance/

famous-twilight-87777

09/22/2020, 6:00 AM

with EC2 instances there is a userData64 option https://www.pulumi.com/docs/reference/pkg/aws/ec2/instance/

kind-school-28825

09/22/2020, 6:01 AM

Anyone facing the problem of running the github action workflow file and erroring out about that the Pulumi SDK is not installed?

> Run pulumi/actions                   8s
error: failed to load language plugin nodejs: could not read plugin [/usr/bin/pulumi-language-nodejs] stdout: EOF
Run <docker://pulumi/actions>
/usr/bin/docker run --name pulumiactions_ca0c30 --label 9e3346 --workdir /github/workspace --rm -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY -e PULUMI_ACCESS_TOKEN -e PULUMI_ROOT -e PULUMI_CI -e INPUT_ARGS -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_PATH -e GITHUB_ENV -e RUNNER_OS -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/backend/backend":"/github/workspace" pulumi/actions preview
Logging in using access token from PULUMI_ACCESS_TOKEN
Logged in to <http://pulumi.com|pulumi.com> as qasim (<https://app.pulumi.com/qasim>)
#### :tropical_drink: `pulumi --non-interactive preview`
Previewing update (development)

View Live: <https://app.pulumi.com/qasim/core/development/previews/73500177-9c41-4b15-84b9-0708e2895a11>

    pulumi:pulumi:Stack core-development  error: It looks like the Pulumi SDK has not been installed. Have you run npm install or yarn install?
    pulumi:pulumi:Stack core-development  1 message
 
Diagnostics:
  pulumi:pulumi:Stack (core-development):
    error: It looks like the Pulumi SDK has not been installed. Have you run npm install or yarn install?
 
error: failed to load language plugin nodejs: could not read plugin [/usr/bin/pulumi-language-nodejs] stdout: EOF

famous-twilight-87777

09/22/2020, 9:20 AM

I'm having an issue where I need to lookup a value from https://www.pulumi.com/docs/reference/pkg/openstack/keymanager/secretv1/ ie

getSecret

and then read the payload and inject it into a file - this is possible in terraform however I cannot seem to access the payload (it's always a promise)

wet-soccer-72485

09/22/2020, 11:42 AM

Has there ever been any talks to make a VSCode or another IDE integration to display the status of Pulumi activity and kick off new runs?

fierce-memory-34976

09/22/2020, 12:30 PM

Is it possible to configure the secrets provider in code or does it have to be through the command?

bitter-application-91815

09/22/2020, 2:32 PM

Hey guys, is there a way to do this command via pulumi

<https://raw.githubusercontent.com/kubernetes/autoscaler/master/cluster-autoscaler/cloudprovider/aws/examples/cluster-autoscaler-autodiscover.yaml>

like i see the autoscaling in the kubs sdk. Is this horizontalPodScaling ?

bitter-application-91815

09/22/2020, 2:33 PM

and i presume i need to use beta2 v2 ?

ambitious-ambulance-56829

09/22/2020, 4:16 PM

Hey guys, I’m running into a problem with Pulumi since it’s update to 2.10.0. This problem only seems to happen on MacOS since my colleagues use Linux dists and they do not have this type of thing happening on their stacks while running an update. The problem is that all chart helm related resources are preview to be deleted when I’ve any change on any other resource unrelated to the chart itself inside the stack.

ambitious-ambulance-56829

09/22/2020, 4:16 PM

Type                                                            Name                                                   Plan       Info
     pulumi:pulumi:Stack                                             argocd-support
 ~   ├─ aws:iam:Role                                                 argo-cd                                                update     [diff: ~assumeRolePolicy]
     ├─ kubernetes:helm.sh:Chart                                     argo-cd                                                           1 message
 -   │  ├─ kubernetes:core:Secret                                    argo-cd/argocd-secret                                  delete
 -   │  ├─ kubernetes:core:ServiceAccount                            argo-cd/argocd-server                                  delete
 -   │  ├─ kubernetes:core:ConfigMap                                 argo-cd/argocd-rbac-cm                                 delete
 -   │  ├─ kubernetes:core:Service                                   argo-cd/argo-cd-argocd-server                          delete
 -   │  ├─ kubernetes:<http://monitoring.coreos.com:ServiceMonitor|monitoring.coreos.com:ServiceMonitor>           argo-cd/argo-cd-argocd-application-controller          delete
 -   │  ├─ kubernetes:core:Service                                   argo-cd/argo-cd-argocd-application-controller          delete
 -   │  ├─ kubernetes:<http://networking.k8s.io:Ingress|networking.k8s.io:Ingress>                      argo-cd/argo-cd-argocd-server                          delete
 -   │  ├─ kubernetes:core:ConfigMap                                 argo-cd/argocd-ssh-known-hosts-cm                      delete
 -   │  ├─ kubernetes:core:Service                                   argo-cd/argo-cd-argocd-redis                           delete
 -   │  ├─ kubernetes:core:ConfigMap                                 argo-cd/argocd-tls-certs-cm                            delete
 -   │  ├─ kubernetes:core:ServiceAccount                            argo-cd/argocd-application-controller                  delete
 -   │  ├─ kubernetes:apps:Deployment                                argo-cd/argo-cd-argocd-redis                           delete
 -   │  ├─ kubernetes:<http://monitoring.coreos.com:ServiceMonitor|monitoring.coreos.com:ServiceMonitor>           argo-cd/argo-cd-argocd-repo-server                     delete
 -   │  ├─ kubernetes:<http://rbac.authorization.k8s.io:RoleBinding|rbac.authorization.k8s.io:RoleBinding>          argo-cd/argo-cd-argocd-application-controller          delete
 -   │  ├─ kubernetes:core:Service                                   argo-cd/argo-cd-argocd-repo-server                     delete
 -   │  ├─ kubernetes:core:Service                                   argo-cd/argo-cd-argocd-server-metrics                  delete
 -   │  ├─ kubernetes:apps:Deployment                                argo-cd/argo-cd-argocd-repo-server                     delete
 -   │  ├─ kubernetes:core:Service                                   argo-cd/argo-cd-argocd-application-controller-metrics  delete
 -   │  ├─ kubernetes:core:Service                                   argo-cd/argo-cd-argocd-repo-server-metrics             delete
 -   │  ├─ kubernetes:core:ConfigMap                                 argo-cd/argocd-cm                                      delete
 -   │  ├─ kubernetes:<http://rbac.authorization.k8s.io:ClusterRoleBinding|rbac.authorization.k8s.io:ClusterRoleBinding>   argo-cd-argocd-application-controller                  delete
 -   │  ├─ kubernetes:<http://rbac.authorization.k8s.io:Role|rbac.authorization.k8s.io:Role>                 argo-cd/argo-cd-argocd-application-controller          delete
 -   │  ├─ kubernetes:<http://rbac.authorization.k8s.io:ClusterRole|rbac.authorization.k8s.io:ClusterRole>          argo-cd-argocd-application-controller                  delete
 -   │  ├─ kubernetes:apps:Deployment                                argo-cd/argo-cd-argocd-server                          delete
 -   │  ├─ kubernetes:<http://rbac.authorization.k8s.io:ClusterRoleBinding|rbac.authorization.k8s.io:ClusterRoleBinding>   argo-cd-argocd-server                                  delete
 -   │  ├─ kubernetes:<http://monitoring.coreos.com:ServiceMonitor|monitoring.coreos.com:ServiceMonitor>           argo-cd/argo-cd-argocd-server                          delete
 -   │  ├─ kubernetes:<http://rbac.authorization.k8s.io:RoleBinding|rbac.authorization.k8s.io:RoleBinding>          argo-cd/argo-cd-argocd-server                          delete
 -   │  ├─ kubernetes:core:ServiceAccount                            argo-cd/argocd-dex-server                              delete
 -   │  ├─ kubernetes:<http://rbac.authorization.k8s.io:ClusterRole|rbac.authorization.k8s.io:ClusterRole>          argo-cd-argocd-server                                  delete
 -   │  ├─ kubernetes:<http://rbac.authorization.k8s.io:Role|rbac.authorization.k8s.io:Role>                 argo-cd/argo-cd-argocd-server                          delete
 -   │  └─ kubernetes:apps:Deployment                                argo-cd/argo-cd-argocd-application-controller          delete
     ├─ kubernetes:yaml:ConfigFile                                   project
     │  └─ kubernetes:<http://apiextensions.k8s.io:CustomResourceDefinition|apiextensions.k8s.io:CustomResourceDefinition>  <http://appprojects.argoproj.io|appprojects.argoproj.io>                                           1 warning
     └─ kubernetes:yaml:ConfigFile                                   application
        └─ kubernetes:<http://apiextensions.k8s.io:CustomResourceDefinition|apiextensions.k8s.io:CustomResourceDefinition>  <http://applications.argoproj.io|applications.argoproj.io>                                          1 warning

ambitious-ambulance-56829

09/22/2020, 4:16 PM

E.g, I’m updating a IAM Role for this stack and all Chart Helm related resources are previewing with a deletion plan for it but the IAM Role is not even being set on any Chart value. By running an refreesh on the same stack it show me that there are no changes to be made in

kubernetes:helm.sh:Chart

nor its dependencies. However when I run an update specifying a single resource URN to update (in this case the

aws:iam:Role

one) it will run without problems and then trying to update it again no changes are shown anymore, no delete plan for the chart resources anymore. Do you guys have any idea on what could I’ve been wrong or am I missing something? Thanks in advance for the help.

clever-plumber-29709

09/22/2020, 4:44 PM

I was checking awsx vpc for reference https://github.com/pulumi/pulumi-awsx/blob/master/nodejs/awsx/ec2/vpc.ts, but i couldn't find how they create the eip used for the nat gateways, can someone point me on how they do it?

bitter-application-91815

09/22/2020, 5:32 PM

Any examples how to configure how to use a private container registry (in this case self hosted gitlab) to roll out images onto aws eks stack

bitter-application-91815

09/22/2020, 5:33 PM

https://github.com/pulumi/examples/blob/master/azure-ts-aks-keda/keda.ts#L32-L50