fix: auto member join for mongodb

[wallyxjh]

Issue:
After directly updating Cluster replicas, MongoDB keeps only the primary; secondaries never join. Pods are Running but have no role label and the component stays Updating.

Root Cause:
memberJoin is triggered only via annotation; when scale-out is bypassed and ClusterDefinition doesn’t define memberJoin, join never runs. The detection was also too strict (Ready-only), creating a deadlock.

Fix:

1. Auto-detect pods that should join when the annotation is empty
2. For MongoDB, allow join even if lifecycleActions.memberJoin is not defined
3. Relax detection to include Running pods
4. Allow doMemberJoin to execute without explicit memberJoin config for MongoDB

Impact:
Limited to MongoDB components (CharacterType=mongodb with roleProbe builtinHandler=mongodb). Other engines are unaffected.

Code:
controllers/apps/transformer_component_workload.go

Verification:
Trigger reconcile, confirm controller logs show “detected pods to member join”, and validate pod role labels + rs.status members are complete.

Tests:
Not run (manual verification via reconcile + role labels + rs.status).

If you want, I can also provide a shorter “summary + test plan” version.

[Copilot]

Pull request overview

This pull request fixes a critical issue where MongoDB secondary pods fail to join the cluster after direct replica updates, leaving them in a Running state without role labels while the component remains in Updating status.

Changes:

• Introduced auto-detection of pods that should join the cluster when the annotation is empty
• Added special handling for MongoDB to enable member join operations without explicit MemberJoin lifecycle action configuration
• Relaxed pod detection criteria to include Running pods (not just Ready pods)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.