The quickstarts as written now do not account for the fact that the provider pod (e.g. the S3 provider pod in the AWS quickstart) throws an RBAC error when the managed resource is created. This can be assumed to affect each quickstart (AWS and GCP tested manually so far).
The error is k8s.io/client-go@v0.30.0/tools/cache/reflector.go:232: failed to list *v1beta1.ProviderConfig: providerconfigs.aws.upbound.io is forbidden: User "system:serviceaccount:crossplane-system:provider-aws-s3-f388c2201fc3" cannot list resource "providerconfigs" in API group "aws.upbound.io" at the cluster scope.
See #887 for more context.
The quickstarts as written now do not account for the fact that the provider pod (e.g. the S3 provider pod in the AWS quickstart) throws an RBAC error when the managed resource is created. This can be assumed to affect each quickstart (AWS and GCP tested manually so far).
The error is
k8s.io/client-go@v0.30.0/tools/cache/reflector.go:232: failed to list *v1beta1.ProviderConfig: providerconfigs.aws.upbound.io is forbidden: User "system:serviceaccount:crossplane-system:provider-aws-s3-f388c2201fc3" cannot list resource "providerconfigs" in API group "aws.upbound.io" at the cluster scope.See #887 for more context.