Custom Service

This destination type routes traffic to any Kubernetes service running in the cluster — it does not have to be managed by CodeNOW. This is useful for routing to infrastructure services, third-party tools, or any workload deployed directly to the cluster.

1 — Rule — the URL path prefix to match (e.g. /custom)

2 — Custom Destination — toggle to switch from Application Component to Custom Service mode

3 — Host — the Kubernetes service name; resolved internally as <host>.svc.cluster.local

4 — Port — the port the Kubernetes service listens on

5 — HTTPS Redirect — when enabled, HTTP requests are automatically redirected to HTTPS

6 — Rewrite Context Path — when enabled, specify the Context Path that the matched prefix will be rewritten to before the request is forwarded