🐛 Reorder engagement logic for 'aware' in clusters.go

[EpicStep]

Problem

Resource reconciliation was intermittently triggered before the indexer had initialized, leading to reconcile errors like 'Index with name X does not exist'.

Fix

Reordered Engage and indexer initialization so that the indexer is fully ready before reconciliation begins.

Note

I haven't done a deep dive into the surrounding source code, so there may be side effects or risks I'm not aware of. If you see any potential issues with this change, please flag them - I'm happy to resolve them myself.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: EpicStep / name: Stepan Rabotkin (208a511)

[k8s-ci-robot]

Welcome @EpicStep!

It looks like this is your first PR to kubernetes-sigs/multicluster-runtime 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/multicluster-runtime has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[embik]

/approve

Thank you for the contribution! This looks good and makes sense to me.

[k8s-ci-robot]

LGTM label has been added.

Details

Git tree hash: ed1155c21e4415d2187e11881f597b43f8757a03

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: embik, EpicStep

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [embik]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment