Need some checkpoints of controller runtime

[kdada]

The workflow of controller manager:

go startNonLeaderElectionRunnables
  -> waitForCache
  -> start nonLeaderElectionRunnables
[After leader election]go startLeaderElectionRunnables
  -> waitForCache
  -> start leaderElectionRunnables

I want to initialize something after cache ready and before starting runnables. So I need some check points:

go startNonLeaderElectionRunnables
  -> // Check point 1
  -> waitForCache
  -> // Check point 2
  -> start nonLeaderElectionRunnables
[After leader election]go startLeaderElectionRunnables
  -> // Check point 3
  -> waitForCache
  -> // Check point 4
  -> start leaderElectionRunnables

Then I can build global memory cache before starting controllers and webhooks. WDYT?

[DirectXMan12]

You could always wrap your controller in a separate runnable. What, exactly, are you trying to accomplish here?

[vincepri]

/priority awaiting-more-evidence
/milestone Next

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[vincepri]

Closing due to inactivity, feel free to reopen if necessary.

/close

[k8s-ci-robot]

@vincepri: Closing this issue.

In response to this:

Closing due to inactivity, feel free to reopen if necessary.

/close

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.