Hi, we built our own crd package with the `crd2pul...
# pulumi-kubernetes-operator
p
Hi, we built our own crd package with the
crd2pulumi
cli (to a nodejs project) and there is a weird behavior that I can’t get to wrap my head around: When previewing a deployement, Pulumi tries to install
pulumi resource kubernetes
with the version of my custom plugin… even tho the plugin should already have been installed.
Copy code
@ previewing update....
    pulumi:providers:kubernetes default_0_0_14_c049b797_0  error: Could not automatically download and install resource plugin 'pulumi-resource-kubernetes' at version v0.0.14-c049b797.0, install the plugin using `pulumi plugin install resource kubernetes v0.0.14-c049b797.0`.
    pulumi:providers:kubernetes default_0_0_14_c049b797_0  1 error
    pulumi:pulumi:Stack prometheus-sandbox11.us-east-1  
Diagnostics:
  pulumi:providers:kubernetes (default_0_0_14_c049b797_0):
    error: Could not automatically download and install resource plugin 'pulumi-resource-kubernetes' at version v0.0.14-c049b797.0, install the plugin using `pulumi plugin install resource kubernetes v0.0.14-c049b797.0`.
    Underlying error: error downloading plugin kubernetes to file: failed to download plugin: kubernetes-0.0.14-c049b797.0: 403 HTTP error fetching plugin from <https://get.pulumi.com/releases/plugins/pulumi-resource-kubernetes-v0.0.14-c049b797.0-linux-amd64.tar.gz>
Obviously this won’t work but it’s very unclear where the heck does Pulumi thinks it needs to re-install the version of the kubernetes plugin and why on earth would that link with my crd version 🤷‍♂️ 😅 Anyone knows how to resolve this?
I was able to gather more info from the logs, but still it’s hard to make sense out of it 🤔
g
That looks like a bug. Could you please file an issue? (Pulumi automatically tries to install a plugin version matching your program dependencies, but clearly something is going wrong here)