Networking

This page describes how network communication works in Catalyst for participants, domains, and applications. Components running inside the cluster communicate using Kubernetes internal DNS names, while selected services and APIs can also be exposed externally through ingress routes.

Participants

For every participant running on Catalyst, the following (internal) endpoints are available:

Endpoint	Address
Ledger API	<canton-participant-name>.<namespace>.svc.cluster.local:5011
Admin API	<canton-participant-name>.<namespace>.svc.cluster.local:5019
HTTP JSON API (internal)	jsonapi-<canton-participant-name>.<namespace>.svc.cluster.local:7011
HTTP JSON API (external)	http(s)://<canton-participant-name>.<your-domain>

Default ports are shown above. If you set custom ports when creating a participant, the values will differ.

Domains

For every domain running on Catalyst, the following (internal) endpoints are available:

Endpoint	Address
Public API	<canton-domain-name>.<namespace>.svc.cluster.local:5018
Admin API	<canton-domain-name>.<namespace>.svc.cluster.local:5019
Ingress (if enabled)	http(s)://<canton-domain-name>.<your-domain>

Default ports are shown above. If you set custom ports when creating a domain, the values will differ.

Applications

For every application running on Catalyst, the following endpoints are available:

Type	Address
Internal	<application-name>.<namespace>.svc.cluster.local:80
Backend app	http(s)://<subdomain>.<your-domain>/<application-name>/api
Frontend app	http(s)://<subdomain>.<your-domain>/<application-name>

The default port (80) is used above. If you set a custom port when creating an application, the value will differ.

---