Support Parallel Operator Instances via Watch-Filter

[afritzler]

Summary

Support running multiple metal-operator instances against a single API server, where each instance reconciles only the objects that match its ownership filter. This is a pure predicate/label filter: there is no automatic assignment, no hashing, no rebalancing. An instance either owns objects carrying its label value (metal.ironcore.dev/watch-filter: <name>) or, when unconfigured, objects carrying no watch-filter label at all.

Instances must not interfere with each other: no duplicate reconciles, no fighting over status/labels/finalizers, no cross-instance BMC/Redfish
operations.

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• Sharded Operator Mode #1071

🔗 Related PRs

#1072 - Add sharded operator mode via --shard flag and label-scoped cache [open]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!