Add a temporary workaround to get KCP to detect Ready state faster

[fabriziopandini]

User Story

As a developer/user/operator I would like KCP to detect Ready state in a reliable way.

Detailed Description

The KCP Ready state depends by the controller to detect node state changes.

This is going to be addressed by #2880 and by follow up PRs making KCP to use the new remote cluster cache.

However, in the meantime, KCP is somehow unpredictable in detecting Ready state because it mostly depends on the resync loop. This makes bad user experience and it introduces some flakiness in the e2e test due to timeouts hard to tune.

This issue is about introducing a temporary workaround in KCP making the controller to continuously re-queue until the Ready state is reached

/kind feature

[k8s-ci-robot]

@fabriziopandini: The label(s) area/controlplane cannot be applied, because the repository doesn't have them

In response to this:

User Story

As a developer/user/operator I would like KCP to detect Ready state in a reliable way.

Detailed Description

The KCP Ready state depends by the controller to detect node state changes.

This is going to be addressed by #2880 and by follow up PRs making KCP to use the new remote cluster cache.

However, in the meantime, KCP is somehow unpredictable in detecting Ready state because it mostly depends on the resync loop. This makes bad user experience and it introduces some flakiness in the e2e test due to timeouts hard to tune.

This issue is about introducing a temporary workaround in KCP making the controller to continuously re-queue until the Ready state is reached

/area controlplane
/kind feature

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.

[k8s-ci-robot]

@fabriziopandini: The label(s) area/controlplane cannot be applied, because the repository doesn't have them

In response to this:

User Story

As a developer/user/operator I would like KCP to detect Ready state in a reliable way.

Detailed Description

The KCP Ready state depends by the controller to detect node state changes.

This is going to be addressed by #2880 and by follow up PRs making KCP to use the new remote cluster cache.

However, in the meantime, KCP is somehow unpredictable in detecting Ready state because it mostly depends on the resync loop. This makes bad user experience and it introduces some flakiness in the e2e test due to timeouts hard to tune.

This issue is about introducing a temporary workaround in KCP making the controller to continuously re-queue until the Ready state is reached

/area controlplane
/kind feature

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.

[vincepri]

/area control-plane
/milestone v0.3.4

I'd like to get this in v0.3.4, and replace it by #2880 and any follow-up PRs when it's ready.

[benmoss]

/assign @fabriziopandini
#2907