-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
v1.7 backports 2020-06-30 #12337
v1.7 backports 2020-06-30 #12337
Conversation
…ync was successful [ upstream commit e2cd4b7 ] Cloud APIs can get into a bad state. This could result in the operator being restarted. If that happens and the Cloud API synchronization then failed the CiliumNode resource would have its status overwritten. This is not desirable. Require a sucessful Cloud API sync before updating the CiliumNode resource. Fixes: #11052 Signed-off-by: Thomas Graf <thomas@cilium.io> Signed-off-by: Maciej Kwiek <maciej@isovalent.com>
[ upstream commit 7947ac9 ] The initial synchronization is blocking but did not return the error so far. Treat the initial synchronization as critical. If that can't succeed, restart the operator to indicate the problem. IP allocation will not succeed anyway. Signed-off-by: Thomas Graf <thomas@cilium.io> Signed-off-by: Maciej Kwiek <maciej@isovalent.com>
test-backport-1.7 |
cb9d515
to
a5a6460
Compare
test-backport-1.7 |
test-missed-k8s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First two commits look good.
Third commit is a bit less straightforward to trace. I have one question below, would be nice if after your response we have someone else take a look over this PR as well.
…nstable [ upstream commit b5c5ca9 ] It is possible for the cloud APIs being used by the operator to get into a state where POST and PATCH operations are still succeeding while GET operations are failing. This can result in the operator to continously creating resources while being unable to ever synchronize the state successfully. Require a successful synchronization of all resources in order to continue performing mutating operations. Signed-off-by: Thomas Graf <thomas@cilium.io> Signed-off-by: Maciej Kwiek <maciej@isovalent.com>
a5a6460
to
09ed88c
Compare
test-backport-1.7 |
test-missed-k8s |
@joestringer fixed, but I think it would be good to have @tgraf take a look as original author |
Once this PR is merged, you can update the PR labels via: