Closed theocld closed 10 months ago
Idem. Since several hours today the Providers installed are unhealthy. I deleted them and tried to reinstall them but same result.
NAME INSTALLED HEALTHY PACKAGE AGE
crossplane-provider-aws True False crossplanecontrib/provider-aws:v0.44.1 6m40s
crossplane-provider-helm True False crossplanecontrib/provider-helm:v0.15.0 6m40s
crossplane-provider-kubernetes True False crossplanecontrib/provider-kubernetes:v0.9.0 6m40s
Crossplane version: 1.13.2
If there are any issues regarding the installation you need to look at the ProviderRevision
resource that contains the actual errors messages: kubectl get providerrevision | grep aws
.
Unfortunately, I'm not learning anything significant about a possible error...
@theocld you have to check the events using kubectl describe
.
And by the way, I believe you are looking into the wrong provider. xpkg.upbound.io/upbound/provider-aws
refers to https://github.com/upbound/provider-aws which is the official provider by Upbound that is generated with TerraJet. This repository here contains the community-supported "hand-written" provider for AWS using the plain AWS Go SDK.
Yes, that was it. It was the wrong package. I used the AWS quickstart package and the prividers were healthy. Thank you.
What happened?
I wanted to install the AWS provider by following the upbound documentation via shell commands. After several attempts, the "kubectl get provider" command systematically tells me that the provider's health is unknown (Health unknown, Installed true). "Kubectl describe provider" only gives me the warning "UnknownPackageRevisionHealth". I've followed the shell commands exactly, but I don't understand where this error comes from.
What environment did it happen in?
Crossplane version: latest Cloud provider: AWS Kubernetes version: v1.26.9+rke2r1 Kubernetes distribution: RKE2 Kernel: Linux master 5.8.0-63-generic