[Toolhive Operator] MCPRegistry: Issues after upgrading to `v0.23.1`

[aRobinson-R7]

Two issues noticed when deploying the Registry via the Toolhive Operator after upgrading to v0.23.1 (from an alpha deployment)

1. Failing Liveness and Readiness probes:
   As per Remove internal-only endpoints from OpenAPI docs toolhive-registry-server#722 these endpoints are only served on 8081, not the original 8080 where the rest of the API lives.
   When upgrading or deploying a new registry, these are still being set to port 8080 and the Registry is being replaced when the liveness probes reach their limit.
   Workaround - manually edit the MCPRegistry deployment to use the correct ports

2. Registry source still requires format: upstream to be set
   Documentation no longer lists the format when configuring this and there is a PR where it mentions this field has not been required and is no longer needed. Getting the following logs in the registry pod when the format field is not included:

{"time":"2026-04-22T14:56:56Z","level":"INFO","msg":"Starting sync operation","registry":"rapid7"}
{"time":"2026-04-22T14:56:56Z","level":"INFO","msg":"Starting git clone","repository":"<repo_name>,"branch":"main","tag":"","commit":""}
{"time":"2026-04-22T14:56:57Z","level":"INFO","msg":"Git clone completed","repository":"<repo_name>","duration":"229.443736ms","branch":"main","commit_sha":"<sha>"}
{"time":"2026-04-22T14:56:57Z","level":"INFO","msg":"Memory stats after operation","alloc_mb":4,"delta_mb":0,"sys_mb":21,"heap_alloc_mb":4,"heap_sys_mb":15,"heap_idle_mb":8,"heap_released_mb":6}
{"time":"2026-04-22T14:56:57Z","level":"ERROR","msg":"Fetch operation failed","error":"registry data validation failed: unsupported format: "}
{"time":"2026-04-22T14:56:57Z","level":"ERROR","msg":"Sync failed","registry":"rapid7","error":"Fetch failed: registry data validation failed: unsupported format: "}

Operator Chart Version: 0.23.1
Operator CRD Chart Version: 0.23.1
Operator Image Version: v0.23.1
Registry Image Version: v1.1.1

[rdimitrov]

Hey, @aRobinson-R7, thanks for reaching out! 👋 I appreciate the detailed information, I'll have a look at these tomorrow and I'll get back to you 👍 Cheers!