Anyone seen this before? Using the automation API in node.

+  kubernetes:core/v1:Namespace aaa-7f creating error: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: Get "...": getting credentials: exec: fork/exec /usr/local/bin/aws: no such file or directory

Pulumi running in a docker container. First i thought it was because I was using alpine, but in a debian image it does the same thing. Manually running the aws cli works fine

root@alpha-launchpad-5d89b45bdc-nz5pp:/usr/src/app# aws --version
aws-cli/2.1.36 Python/3.8.8 Linux/5.4.89+ exe/x86_64.debian.9 prompt/off
root@alpha-launchpad-5d89b45bdc-nz5pp:/usr/src/app# /usr/local/bin/aws --version
aws-cli/2.1.36 Python/3.8.8 Linux/5.4.89+ exe/x86_64.debian.9 prompt/off

I’ve seen similar things happen before when shelling out from node for other apps if I did not force the shelled out command to use bash as a shell.

is this when it is running in AWS, or when it is running locally?

The error happens in a container, running on GKE

I'm thinking it is related to this then: https://github.com/pulumi/pulumi-aws/issues/1359

Fairy sure it is not related to credentials, this is before it needs credentials. It cannot launch the AWS binary. Nothing in that issue is close to the error I’m seeing.

I'm seeing

getting credentials:

in the original error you mentioned as well as this

unable to load schema information from the API server

so maybe I'm not seeing the same thing you are

check the end of that line

Yes I roger that. I was thinking that maybe it was looking locally for creds because the API check for creds and the inferred EC2 check for creds were disabled by default. Anyways, sorry If I led you astray. Good luck!

Ok, /usr/local/bin/aws is a symlink, i modified the path so it chose the real binary first

# which aws
/usr/local/aws-cli/v2/current/bin/aws

but out of the automation api i still get

fork/exec /usr/local/bin/aws: no such file or directory