feat(helm): add useLegacyGRPCEndpoints to select client endpoints

Merged
MI
2d ago
+382-73

Add the top-level useLegacyGRPCEndpoints value to the open source chart, with the same name and behavior as in the chainloop-ee chart (chainloop-dev/platform#7278).

  • The value selects the endpoints that the clients use: the control plane connection to the CAS (cas_server.grpc.addr) and the chainloop config save command in the install notes (NOTES.txt).
  • The default is true. The clients keep the deprecated gRPC-only endpoints (ingressAPI, serviceAPI), and the rendered defaults do not change.
  • Set it to false to use the shared endpoints (ingress, service), which serve HTTP and native gRPC on one hostname. Only an explicit false selects them, because helm upgrade --reuse-values from an older chart leaves the key unset. A later release changes the default to false.
  • The chart keeps the deprecated endpoints in both modes, so existing CLIs continue to work.
  • The README documents the deprecation of the gRPC-only endpoints and the steps to move to the shared endpoints. The ingressAPI.enabled and serviceAPI.type parameters are marked as deprecated.
Rendered diffs (base 1.489.0 vs head 1.489.1)

All renders use development=true. The diffs ignore the chart version labels, the dev-mode secrets that are random on every render, and the checksums that follow from them. NOTES.txt is rendered too. Scenarios: no Ingress (ClusterIP), all four Ingresses with TLS, NodePort Services, LoadBalancer Services.

Default values, and useLegacyGRPCEndpoints=true: no diff in any scenario.

useLegacyGRPCEndpoints=false, all four Ingresses with TLS:

-        addr: t-chainloop-cas-api:80
+        addr: t-chainloop-cas:80
...
-      --control-plane cp-api.ex.com:443 \
-      --artifact-cas cas-api.ex.com:443
+      --control-plane cp.ex.com:443 \
+      --artifact-cas cas.ex.com:443

useLegacyGRPCEndpoints=false, no Ingress:

-        addr: t-chainloop-cas-api:80
+        addr: t-chainloop-cas:80
...
-       kubectl port-forward --namespace default svc/t-chainloop-controlplane-api 9000:80 &
+       kubectl port-forward --namespace default svc/t-chainloop-controlplane 9000:80 &
...
-       kubectl port-forward --namespace default svc/t-chainloop-cas-api 9001:80 &
+       kubectl port-forward --namespace default svc/t-chainloop-cas 9001:80 &

With LoadBalancer and NodePort Services, the install notes read the shared Services (t-chainloop-controlplane, t-chainloop-cas) and their node ports.

AI disclosure: this change was produced with assistance from Claude Code.

closes https://linear.app/chainloop/issue/PFM-7958