proud-pizza-80589
04/11/2021, 9:07 PM+ 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.bored-oyster-3147
04/11/2021, 9:15 PMproud-pizza-80589
04/11/2021, 9:17 PMbored-oyster-3147
04/11/2021, 9:19 PMSkipMetadataApiCheck
and SkipGetEc2Platforms
to be set to false
. The defaults were changed because performing those checks every run was a performance hit so the defaults were changed to true
recentlyproud-pizza-80589
04/11/2021, 9:22 PMbored-oyster-3147
04/11/2021, 9:23 PMgetting 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 areproud-pizza-80589
04/11/2021, 9:24 PMexec: fork/exec /usr/local/bin/aws: no such file or directory
bored-oyster-3147
04/11/2021, 9:26 PMproud-pizza-80589
04/12/2021, 7:12 AM# 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