-
Notifications
You must be signed in to change notification settings - Fork 268
EC2 controller - crash loop back off - when upgrading to 1.2.2 #2007
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
Comments
Logs are attached
|
@a-hilaly Hi! Just two observations
|
The same with controllers: eks-controller @1.2.1 route53-controller - the same effect... |
Hi @gecube !
This is a controller-runtime behaviour.. In each controller, there will be one reconciler per CRD - each one of them will complain if the CRD is not installed.
Yeah i completly agree here.. very likely we will build an ACK operator to handle ACK controllers deployment.. and it will not rely on helm. |
@gecube Just double checking, this is not a crash loopback off right? just errors about missing CRDs? |
@a-hilaly Hi! I am kindly asking also add tags for eks/iam/lambda/route53 controllers, as all of them are affected. Regarding your question - it is error about missing CRDs leading to crash loopback off. Please refer to the screenshots above with openshift console. |
AFAIK eks and iam supports tags update. I just pinged the lambda service team to check with their controller. |
@gecube we've made some updates to the helm charts and permission in the last releases. Maybe a reinstallation of the controller could help? |
@a-hilaly yes, I have already fixed the issue - #2007 (comment) |
Hey @gecube, |
@gecube AFAIK helm won't update or delete the CRDs Closing since the helm chart is fixed in recent versions |
@a-hilaly: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Good day!
Today I noticed that EC2 controller was updated:
to the version 1.2.2
In the meantime EC2 controller pod begin to fail:
The text was updated successfully, but these errors were encountered: