pulumi-community #general

best-crayon-38951

02/16/2020, 3:40 PM

Hi guys, I installed the pulumi cli on a new machine, and then ran my

pulumi up -s <stack>

command which resulted in:

Copy code

error: could not load plugin for gcp provider 'urn:pulumi:dev::tip::pulumi:providers:gcp::default_2_3_0_alpha_1579304739': no resource plugin 'gcp-v2.3.0-alpha.1579304739' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource gcp v2.3.0-alpha.1579304739`

However, when I run

pulumi plugin ls

I get:

Copy code

NAME        KIND      VERSION  SIZE   INSTALLED  LAST USED
gcp         resource  2.5.0    79 MB  n/a        18 minutes ago

Which is newer. I've tried running

pulumi plugin install resource gcp v2.3.0-alpha.1579304739

as instructed, by it resulted in "Not found". Then, I've tried running

pulumi plugin install resource gcp v2.3.0

but it still failed because it seems I need a very specific version. How should I solve this? Thanks in advance.

white-tailor-63592

02/16/2020, 6:07 PM

Hey guys, who’s off to Kubecon in Amsterdam next month? Hopefully see some of you at the Pulumi pre-day 👍🏼

☝️ 2

breezy-butcher-78604

02/17/2020, 1:43 AM

when I configure a Pulumi org with Okta authentication, is it possible for anyone to log into the org with a non-sso user?

nice-guitar-97142

02/17/2020, 4:00 PM

hey guys, we are trying to add seats to our org in the app, and https://app.pulumi.com/insertOrgName/people/settings throws a 404.

some-art-311

02/17/2020, 6:16 PM

Anyone by chance know this issue ? What I did was just updated pulumi versions

Copy code

"@pulumi/aws": "1.13.0 -> "1.22.0",
    "@pulumi/eks": "0.18.16" -> "0.18.21",
    "@pulumi/kubernetes": "1.3.3" -> "1.5.2",
    "@pulumi/pulumi": "1.6.1" -> "1.10.1",

some-art-311

02/17/2020, 6:17 PM

limited-rainbow-51650

02/17/2020, 7:30 PM

Is there a way to access the Pulumi state graph programmatically? Context: https://github.com/mingrammer/diagrams/issues/1#issuecomment-587075671

quaint-book-39362

02/17/2020, 7:45 PM

hi, guys. i'm trying to do a very simple pulumi program where i install a kong helm chart to an existing k8s cluster (KinD) and, although i don't get any errors, the artifacts aren't created on my cluster

quaint-book-39362

02/17/2020, 7:45 PM

Copy code

import * as k8s from '@pulumi/kubernetes';

const kong = new k8s.helm.v3.Chart('kong', {
  fetchOpts: {
    repo: '<https://charts.konghq.com>',
  },
  chart: 'kong',
  values: {
    ingressController: {
      installCRDs: false,
    },
    proxy: {
      type: 'NodePort',
      http: {
        nodePort: 31500,
      },
      tls: {
        nodePort: 32500,
      },
    },
  },
});

quaint-book-39362

02/17/2020, 7:45 PM

that's the code

quaint-book-39362

02/17/2020, 7:45 PM

and preview:

quaint-book-39362

02/17/2020, 7:45 PM

quaint-book-39362

02/17/2020, 7:46 PM

also, not sure why that preview mentions helm v2, when i specified v3

quaint-book-39362

02/17/2020, 7:47 PM

this is what i do via the command line and it works fine:

Copy code

# helm repo add kong <https://charts.konghq.com>
# helm repo update
# helm install kong/kong --generate-name --set ingressController.installCRDs=false,proxy.type=NodePort,proxy.http.nodePort=31500,proxy.tls.nodePort=32500

quaint-book-39362

02/17/2020, 7:53 PM

basically with command line, after running the install if i do

kubectl get all -A | grep kong

i can see several artifacts including kong pods and others. with pulumi i see nothing.

quaint-book-39362

02/17/2020, 7:56 PM

i am not sure if i need to supply a

provider

for the k8s cluster, but i believe it is not necessary if

kubectl

already points to it

quaint-book-39362

02/17/2020, 7:57 PM

at least according to this: https://www.pulumi.com/docs/get-started/kubernetes/configure/

future-monkey-81011

02/17/2020, 11:52 PM

hey pulumi, which VS Code theme are you guys using here?

icy-london-58403

02/18/2020, 8:27 AM

I followed the guide on dynamic providers and I have it working fairly well. I am making a dynamic provider for IPAM (IP Address Management). I've wrapped Netbox with typescript and I my dynamic provider calls my wrapper for CRUD. Everything creates and updates great and everything destroys if I use the

pulumi destroy

command. But if I comment out one of my custom resources, it tries to connect to it with default provider values. I pass the provider a token and a url. I can tell by the errors that it is defaulting to localhost port 80 with no token. So it seems the provider doesn't hold onto these values in the state and it needs the code to know these values during deletions. Is this normal behaviour or is there something I can do to enhance my setup?

handsome-actor-1155

02/18/2020, 2:50 PM

Looking at your backlog, I saw: • Overhaul

cloud

for true cross-cloud infrastructure definition This seems really exciting and I'm just curious to what level you're wanting to take it? A single

cloud

provider for all common cloud components like k8s, storage, compute, etc? If so, that seems like it would be a game changer

loud-whale-26029

02/18/2020, 4:12 PM

Hello Everyone, Im having an issue when trying to deploy a new HorizontalPodAutoscaler. we are using Aws EKS version 1.14.7. I have imported the library '@pulumi/kubernetes/autoscaling/v2beta2' and also at the class definition I stated the desired apiVersion ('autoscaling/v2beta2'). The deploy succeeded but when im examining the result, i notice that the apiVersion used is autoscaling/v1, But ... at the metadata section I can see that the last applied configurations gets the correct configuration. any suggestions on why it happens would be appreciated.

limited-rainbow-51650

02/18/2020, 4:16 PM

Call to Pulumi (the company) to have this issue fixed: https://github.com/pulumi/pulumi/issues/3747 As a company using Pulumi (the product) for our end customers, I work with the different Pulumi state setups of our customers. But the need to login/logout each time prevents me from running Pulumi concurrently for multiple customers. As a result, Pulumi (the product) decreases my productivity at the moment. 😢

cool-egg-852

02/18/2020, 5:04 PM

Does pulumi need any specific configuration to be able to create a pubsub topic in GCP? Trying to figure out why only topics are not able to be created but the serviceaccount I use can do everything else. It has the owner role.

thankful-gpu-3329

02/18/2020, 6:54 PM

Hey all

thankful-gpu-3329

02/18/2020, 6:55 PM

I'm trying to use

pulumi login <gs://name-of-my-relevant-bucket>

but am running into issues. I created a new service account and have set

GOOGLE_CREDENTIALS

with the contents of the associated/generated key in my shell, but the cli is still showing the same warning it was prior to creating the service account.

thankful-gpu-3329

02/18/2020, 6:55 PM

Copy code

warning: Pulumi will not be able to print a statefile permalink using these credentials. Neither a GoogleAccessID or PrivateKey are available. Try using a GCP Service Account.
Logged into MBBlack.local as joeyfigaro (<gs://grpc-dummy-stuff-stack>)

thankful-gpu-3329

02/18/2020, 6:58 PM

Okay, I'm a dope.

thankful-gpu-3329

02/18/2020, 6:58 PM

Figured it out.

thankful-gpu-3329

02/18/2020, 6:59 PM

Didn't actually confirm that

GOOGLE_CREDENTIALS

had the expected stuff in it. Turns out it didn't. 😛

😄 1

thankful-gpu-3329

02/18/2020, 6:59 PM

in my case I had

export GOOGLE_CREDENTIALS=$(cat .keystuff/name-of-creds.json)

instead of

export GOOGLE_CREDENTIALS=$(cat ./keystuff/name-of-creds.json)