kura: decide whether the standalone OSS Helm chart should adopt single-host gRPC (currently split-host)

Background

The single-host gRPC change (#11356) moved the Tuist operator (infra/kura-controller) to co-host gRPC on the public host. The standalone Kura OSS Helm chart (kura/ops/helm/kura/) still documents and ships the split-host pattern — a separate grpcIngress block (enabled: false) with kura-grpc.local / kura-grpc.example.com examples (kura/ops/helm/kura/values.yaml, kura/README.md:442).

Flagged (as out of scope) in review of #11356: the public Kura deployment story now diverges from what Tuist ships.

Decision to make

Should the standalone OSS chart also adopt single-host (path-split gRPC + HTTP on one host), or keep offering split-host as an option?

• If align to single-host: add path-split gRPC routing to the public-host Ingress in the chart (use-regex + per-location backend-protocol), deprecate/remove the separate grpcIngress block, and update kura/README.md examples. Note the ingress-nginx dependency (see #11356).
• If keep split-host as an option: document that the OSS chart intentionally supports both, and that single-host is the Tuist-managed default — so users aren’t surprised by the difference.

References

• #11356 (operator single-host change)
• kura/ops/helm/kura/values.yaml (grpcIngress), kura/README.md:442

No GitHub comments yet.