chore: requeue immidiately after creating role #165
Conversation
Currently, after a role is created, we set the synced condition to false, casuing the controller to requeue the resource and proccess any updates in 30 seconds (default requeue on non synced resource) This is not an ideal use case for users who have thousands of resources, and don't want to wait long for their resources to be processed/ready.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: a-hilaly, michaelhtm The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@michaelhtm: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
2 participants
Description of changes:
Currently, after a role is created, we set the synced condition to
false, causing the controller to requeue the resource and process any
updates in 30 seconds (default requeue on non synced resource)
This is not an ideal use case for users who have thousands of resources,
and don't want to wait long for their resources to be processed/ready.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.