This message was deleted.

You ned to make sure you're using the right versions of the pulumi cli and the providers. The earliest version of the kubernetes provider that supports ARM64 (and therefore the M1 chip) is 2.8.3

This is the release version: https://github.com/pulumi/pulumi-kubernetes/blob/master/CHANGELOG.md

If you try to use any earlier version with the version of the Pulumi CLI that supports ARM64 then it returns a 403

The last comment in this will help with troubleshooting: https://github.com/pulumi/pulumi/issues/4868

it actually reported on first try:

[resource plugin kubernetes-2.8.3] installing
Downloading plugin: 25.82 MiB / 25.82 MiB [=========================] 100.00% 8s
 
error: could not load plugin for kubernetes provider 'urn:pulumi:prod-bravo-excelproc::excel-processor::pulumi:providers:kubernetes::default_2_6_1': no resource plugin 'kubernetes-v2.6.1' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource kubernetes v2.6.1`
make: *** [deploy-prod] Error 255

so it looks like it installed 2.8.3 but then wants 2.6.1 of the plugin. running `pulumi plugin install resource kubernetes v2.8.3`returns nothing and the plugin is not installed

What do you see if you run

pulumi plugin ls

?

actually this plugin is listed there:

atli@Atlis-MacBook-Pro-2 pulumi % pulumi plugin ls
NAME        KIND      VERSION  SIZE   INSTALLED       LAST USED
kubernetes  resource  2.8.3    66 MB  38 minutes ago  38 minutes ago

TOTAL plugin cache size: 66 MB

but it always tryes to fetch the old one, will have a look at the package.json mentioned in the github comment

might be worth deleting the package-lock.json and the node_modules folder to be safe

I am bit of a pulumi noob, is this a package.json for pulumi ? (my application is not a node app)

what language are you using?

python

ok, then your requirements.txt

requirements.txt:

pulumi-kubernetes==2.8.3

can you do

pulumi stack export > stack.json

- it's possible that it's in there too. Do you'll need to update that as well

yeah, that has

kubernetes::default_2_6_1

so where it says either 2_6_1 or 2.6.1 you'll have to change to the appropriate version

ok. thanx we will try this

We ended up deploying this with

pulumi-kubernetes==2.8.3

from an intel mac instead of messing around with a massive json file

Does that force it even if you already have a different version of the provider in the stack?

I wiped my pulumi venv, reinstalled with 2.8.3 and made a no-diff

pulumi up

. That was enough to force it in the stack, even though the output didn’t indicate any changes. Now we can deploy from m1 macs

FWIW, this issue only exists the first time we upgrade on arm64 😕

Also maybe a better error handling would have been nice.

hey @adventurous-author-44528 - I'd love it if you could open an issue around that - we should make that better

Thank you!