-
Notifications
You must be signed in to change notification settings - Fork 132
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
[Bug]: Can't install provider-aws 1.0.0 on crossplane versions before 1.14 #1147
Comments
@mbbush thank you for bringing up this, I was able to reproduce this issue with
|
After discussing with the team we think that this is a Crossplane/UXP issue, so I will transfer the issue to the UXP repo. |
@turkenf AFAICT this is because So, TL;DR: I think |
Thanks @phisco 🙏 Linking the correct implementation from provider-kubernetes: crossplane-contrib/provider-kubernetes@c8bbc9e |
FWIW, when we experienced this issue in our EKS cluster, it was running upstream crossplane v1.12.2, not UXP. |
Thank you all for the discussions here and the guidance given. Opened #1157, which implements the following configuration protocol:
@mbbush, I think you've already seen it, but as a workaround, you can use the |
Thanks for the workaround suggestion. I've already opted to instead use this as an excuse to finally upgrade to crossplane 1.14, which I've wanted to do for a long time, but there were always more urgent things to work on. It seems like the kind of thing that would be good to add to the release notes. Maybe @jeanduplessis could do that? |
Is there an existing issue for this?
Affected Resource(s)
No response
Resource MRs required to reproduce the bug
No response
Steps to Reproduce
Create a kind cluster.
Install uxp v1.13.2-up.3
Install provider-aws v0.47.1, including at least one of the provider packages that have conversion webhooks (ec2, rds, elasticache, or a couple others)
Wait for the providers to stabilize
Upgrade the providers to provider-aws v1.0.0
What happened?
The providers which have conversion webhooks got into a crashloop, and never became ready. ec2, rds, elasticache, etc resources become completely unusable.
Relevant Error Output Snippet
Crossplane Version
v1.13.2-up.3 and earlier (I also tested v1.13.2-up.1 and v1.12.3-up.1)
Provider Version
0.47.1 upgrading to 1.0.0
Kubernetes Version
No response
Kubernetes Distribution
Both EKS and Kind
Additional Info
No response
The text was updated successfully, but these errors were encountered: