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
Fix Teleport update reconciliation on status
updates
#34063
Fix Teleport update reconciliation on status
updates
#34063
Conversation
This pull request addresses the issue where the Teleport operator reconciliation runs every time the operator updates the `status` subresource. This continuous reconciliation has led to an infinite loop, causing millions of reconciliations per minute. When an error occurs, such as having invalid role properties, the Operator updates the status and returns an error, which should trigger a rescheduled reconciliation with exponential backoff. The problem arises because the operator failed to enforce a resource generation change, resulting in an immediate trigger of a new reconciliation when the `status` field is updated. This pull request modifies the operator to avoid updating subresources and only trigger updates when there is a change in resource generation. Special thanks to @strideynet for confirming my hypothesis and giving the solution! Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
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.
Might be nice to move meta.SetStatusCondition
into silentUpdateStatus
to reduce the likelihood of this occurring again - otherwise lgtm
done in c433dc9 |
c433dc9
to
bd9b2db
Compare
* Fix Teleport update reconciliation on `status` updates This pull request addresses the issue where the Teleport operator reconciliation runs every time the operator updates the `status` subresource. This continuous reconciliation has led to an infinite loop, causing millions of reconciliations per minute. When an error occurs, such as having invalid role properties, the Operator updates the status and returns an error, which should trigger a rescheduled reconciliation with exponential backoff. The problem arises because the operator failed to enforce a resource generation change, resulting in an immediate trigger of a new reconciliation when the `status` field is updated. This pull request modifies the operator to avoid updating subresources and only trigger updates when there is a change in resource generation. Special thanks to @strideynet for confirming my hypothesis and giving the solution! Signed-off-by: Tiago Silva <tiago.silva@goteleport.com> * return proper status conditions on failures * enforce condition update on silentUpdateStatus --------- Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
* Fix Teleport update reconciliation on `status` updates This pull request addresses the issue where the Teleport operator reconciliation runs every time the operator updates the `status` subresource. This continuous reconciliation has led to an infinite loop, causing millions of reconciliations per minute. When an error occurs, such as having invalid role properties, the Operator updates the status and returns an error, which should trigger a rescheduled reconciliation with exponential backoff. The problem arises because the operator failed to enforce a resource generation change, resulting in an immediate trigger of a new reconciliation when the `status` field is updated. This pull request modifies the operator to avoid updating subresources and only trigger updates when there is a change in resource generation. Special thanks to @strideynet for confirming my hypothesis and giving the solution! Signed-off-by: Tiago Silva <tiago.silva@goteleport.com> * return proper status conditions on failures * enforce condition update on silentUpdateStatus --------- Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
* Fix Teleport update reconciliation on `status` updates This pull request addresses the issue where the Teleport operator reconciliation runs every time the operator updates the `status` subresource. This continuous reconciliation has led to an infinite loop, causing millions of reconciliations per minute. When an error occurs, such as having invalid role properties, the Operator updates the status and returns an error, which should trigger a rescheduled reconciliation with exponential backoff. The problem arises because the operator failed to enforce a resource generation change, resulting in an immediate trigger of a new reconciliation when the `status` field is updated. This pull request modifies the operator to avoid updating subresources and only trigger updates when there is a change in resource generation. Special thanks to @strideynet for confirming my hypothesis and giving the solution! Signed-off-by: Tiago Silva <tiago.silva@goteleport.com> * return proper status conditions on failures * enforce condition update on silentUpdateStatus --------- Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
* Fix Teleport update reconciliation on `status` updates This pull request addresses the issue where the Teleport operator reconciliation runs every time the operator updates the `status` subresource. This continuous reconciliation has led to an infinite loop, causing millions of reconciliations per minute. When an error occurs, such as having invalid role properties, the Operator updates the status and returns an error, which should trigger a rescheduled reconciliation with exponential backoff. The problem arises because the operator failed to enforce a resource generation change, resulting in an immediate trigger of a new reconciliation when the `status` field is updated. This pull request modifies the operator to avoid updating subresources and only trigger updates when there is a change in resource generation. Special thanks to @strideynet for confirming my hypothesis and giving the solution! Signed-off-by: Tiago Silva <tiago.silva@goteleport.com> * return proper status conditions on failures * enforce condition update on silentUpdateStatus --------- Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
* Fix Teleport update reconciliation on `status` updates This pull request addresses the issue where the Teleport operator reconciliation runs every time the operator updates the `status` subresource. This continuous reconciliation has led to an infinite loop, causing millions of reconciliations per minute. When an error occurs, such as having invalid role properties, the Operator updates the status and returns an error, which should trigger a rescheduled reconciliation with exponential backoff. The problem arises because the operator failed to enforce a resource generation change, resulting in an immediate trigger of a new reconciliation when the `status` field is updated. This pull request modifies the operator to avoid updating subresources and only trigger updates when there is a change in resource generation. Special thanks to @strideynet for confirming my hypothesis and giving the solution! * return proper status conditions on failures * enforce condition update on silentUpdateStatus --------- Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
* Fix Teleport update reconciliation on `status` updates This pull request addresses the issue where the Teleport operator reconciliation runs every time the operator updates the `status` subresource. This continuous reconciliation has led to an infinite loop, causing millions of reconciliations per minute. When an error occurs, such as having invalid role properties, the Operator updates the status and returns an error, which should trigger a rescheduled reconciliation with exponential backoff. The problem arises because the operator failed to enforce a resource generation change, resulting in an immediate trigger of a new reconciliation when the `status` field is updated. This pull request modifies the operator to avoid updating subresources and only trigger updates when there is a change in resource generation. Special thanks to @strideynet for confirming my hypothesis and giving the solution! * return proper status conditions on failures * enforce condition update on silentUpdateStatus --------- Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
* Fix Teleport update reconciliation on `status` updates This pull request addresses the issue where the Teleport operator reconciliation runs every time the operator updates the `status` subresource. This continuous reconciliation has led to an infinite loop, causing millions of reconciliations per minute. When an error occurs, such as having invalid role properties, the Operator updates the status and returns an error, which should trigger a rescheduled reconciliation with exponential backoff. The problem arises because the operator failed to enforce a resource generation change, resulting in an immediate trigger of a new reconciliation when the `status` field is updated. This pull request modifies the operator to avoid updating subresources and only trigger updates when there is a change in resource generation. Special thanks to @strideynet for confirming my hypothesis and giving the solution! * return proper status conditions on failures * enforce condition update on silentUpdateStatus --------- Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
This pull request addresses the issue where the Teleport operator reconciliation runs every time the operator updates the
status
subresource. This continuous reconciliation has led to an infinite loop, causing millions of reconciliations per minute. When an error occurs, such as having invalid role properties, the Operator updates the status and returns an error, which should trigger a rescheduled reconciliation with exponential backoff. The problem arises because the operator failed to enforce a resource generation change, resulting in an immediate trigger of a new reconciliation when thestatus
field is updated.This pull request modifies the operator to avoid updating subresources and only trigger updates when there is a change in resource generation.
Fixes #34092
Changelog: Skip Teleport Operator reconciliation on
status
updatesSpecial thanks to @strideynet for confirming my hypothesis and giving the solution!