fix(operator): Repair moco/mysql rename regressions

[jthakkar04]

Summary

Repairs the chain of moco/mysql string mismatches that blocked on-prem installs from getting past MySQL setup. This PR Restores the end-to-end install: MOCO comes up Healthy, the W&B application pods deploy, and OTLP traffic flows from the gorilla services to the Victoria backends.

Testing

We spun up a cluster using:

./hack/scripts/setup_kind.sh ; tilt up

The before/after screenshots show the MySQL infrastructure stand-up succeeding after this PR.

Before:

We can notice the WeightsAndBiases CR's MYSQL column is empty and kubectl get mysqlcluster returns no resources — the operator never successfully created the cluster.

After:

We can notice the MYSQL reads Healthy and the wandb-moco MySQLCluster shows AVAILABLE=True, HEALTHY=True — which unblocks the rest of the install downstream.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ed10ac9f-050b-4a51-ad16-8807b55a3592

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jthakkar/moco-fixes

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}