feat(chart): opt in to shared control plane and CAS client endpoints

MI
4h ago
+97-39

Add useSharedEndpoints, an opt-in chart flag that defaults to false. It follows the same approach as the chainloop-ee chart (chainloop-dev/platform#6964). When the flag is on:

  • The control plane connects to the CAS through the shared CAS Service (<release>-cas:<service port>), not through the gRPC-only -api Service.
  • The installation notes show the shared ingress hostnames (or the shared Service NodePort) as the CLI addresses.

The flag changes client selection, not endpoint exposure. The legacy serviceAPI and ingressAPI settings remain functional and are now marked deprecated. Their removal belongs to a later release, after existing clients migrate. Disabling the flag restores the previous client endpoint selection, and the defaults render the same output as before.

The chart README now says that the control plane and CAS have served gRPC and HTTP on one port since v1.126.0 (chart 1.469.0). The custom-domain examples now use the shared ingresses. A new "Opt in to shared client endpoints" section describes the migration.

Related: #3628

AI assistance: this change was prepared with Claude Code.