Fix orchestrator and template manager health checks

[djeebus]

• use provider=nomad explicitly
• grpc is only supported by consul-integrated nomad clusters, use http instead
• add tcp health check for orchestrator proxy port
• use network block to define orchestrator ports (similar to template manager)

Before:

After:

---

Note

Replace gRPC health checks with HTTP, add Nomad-labeled ports/provider, use NOMAD_PORT envs, and add TCP check for orchestrator proxy.

• Nomad jobs:
  • Orchestrator (iac/provider-gcp/nomad/jobs/orchestrator.hcl):
    • Add network block with mode = "host" and labeled ports api and proxy (static).
    • Update services to use port labels (api, proxy) and provider = "nomad".
    • Change health checks: orchestrator from grpc to HTTP GET /health; add TCP check for orchestrator-proxy.
    • Use dynamic port envs: GRPC_PORT=$${NOMAD_PORT_api}, PROXY_PORT=$${NOMAD_PORT_proxy}.
  • Template Manager (iac/provider-gcp/nomad/jobs/template-manager.hcl):
    • Rename network port to api and reference it in the service; set provider = "nomad".
    • Change health check from grpc to HTTP GET /health.
    • Use dynamic port env: GRPC_PORT=$${NOMAD_PORT_api}.

^{Written by Cursor Bugbot for commit 13bf326. This will update automatically on new commits. Configure here.}

[djeebus]

This format is exactly the same as the one for template-manager, and allows us to refer to ports by name instead of number

[djeebus]

This enables the health checks to work. Without it, we default to consul, which doesn't function.

[djeebus]

GRPC only works when provider=consul, but we expose an http health endpoint as well.

[djeebus]

Don't need this, as we're using HTTP (not GRPC) and it inherits the port of the service block that surrounds the check.

[djeebus]

Use TCP to ensure that the port is accepting connections

[djeebus]

This refers to the ports defined in the network block on line 8.