-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ProviderRevision failing and Provider is Unhealthy #1325
Comments
Redeploying the cluster and this worked. |
@anfoxtrot I'm having the same issue every time I want to upgrade the aws-provider. What do you mean with "Redeploying the cluster and this worked."?! |
I am also having the same problem! Any solution for this? Update: I actually managed to fix it and that is how I did it: Describe the ProviderRevision CRD:
Then saw the following message:
And following this comment here I just deleted the CRD:
After that it worked like a charm! What I got from it is that the new provider version has an updated version of the CRD (API version) which is not automatically deleted and that makes the provider fail. After deleting the old CRD the provider manages to install the CRD again and everything works! |
Thank you! Deleting the crd worked for me as well. |
Hi,
The same warning with Bucket and other. |
If CRDs (Custom Resource Definitions) are deleted, all resources created from those CRDs will also be removed. |
If your CRDs are in use and you've removed the old provider, just removing the ownerReferences on the CRDs seems to do the trick as well |
What happened?
After applying
A ProviderRevision was created
How can we reproduce it?
Create an EKS cluster
Create an EKS serviceIAMAccount
Install helm chart for crossplane
chart: crossplane
repoURL: https://charts.crossplane.io/stable
targetRevision: 1.8.0
apply
What environment did it happen in?
Crossplane version: 1.8.0
EKS kubernetes: 1.22
The text was updated successfully, but these errors were encountered: