diff --git a/platform-enterprise_docs/enterprise/_templates/k8s/tower-svc.yml b/platform-enterprise_docs/enterprise/_templates/k8s/tower-svc.yml index 04d18ef07..bac2a8fc8 100644 --- a/platform-enterprise_docs/enterprise/_templates/k8s/tower-svc.yml +++ b/platform-enterprise_docs/enterprise/_templates/k8s/tower-svc.yml @@ -108,6 +108,26 @@ spec: selector: app: backend --- +# +# Backend API Service (Optional) +# +# This service exposes the backend API directly if you wish to have a separate +# API endpoint (e.g., api.cloud.seqera.io) distinct from the main frontend. +# +# When to use this: +# - You want a dedicated subdomain for API/CLI access (e.g., api.yourcompany.com) +# - You need to separate API traffic from web UI traffic +# +# Required configuration when enabled: +# - Configure appropriate ingress rules for the API subdomain +# - Ensure your DNS points the API subdomain to this service +# +# Note: This service is optional. Most deployments do not need this unless +# you intentionally want to expose the backend API via a dedicated subdomain. +# If not needed, you can remove this service to simplify your deployment and +# avoid potential routing conflicts with the frontend's wildcard setup. +# +--- apiVersion: v1 kind: Service metadata: diff --git a/platform-enterprise_versioned_docs/version-23.1/enterprise/_templates/k8s/tower-svc.yml b/platform-enterprise_versioned_docs/version-23.1/enterprise/_templates/k8s/tower-svc.yml index cff74e7af..a91803ace 100644 --- a/platform-enterprise_versioned_docs/version-23.1/enterprise/_templates/k8s/tower-svc.yml +++ b/platform-enterprise_versioned_docs/version-23.1/enterprise/_templates/k8s/tower-svc.yml @@ -98,6 +98,26 @@ spec: selector: app: backend --- +# +# Backend API Service (Optional) +# +# This service exposes the backend API directly if you wish to have a separate +# API endpoint (e.g., api.cloud.seqera.io) distinct from the main frontend. +# +# When to use this: +# - You want a dedicated subdomain for API/CLI access (e.g., api.yourcompany.com) +# - You need to separate API traffic from web UI traffic +# +# Required configuration when enabled: +# - Configure appropriate ingress rules for the API subdomain +# - Ensure your DNS points the API subdomain to this service +# +# Note: This service is optional. Most deployments do not need this unless +# you intentionally want to expose the backend API via a dedicated subdomain. +# If not needed, you can remove this service to simplify your deployment and +# avoid potential routing conflicts with the frontend's wildcard setup. +# +--- apiVersion: v1 kind: Service metadata: diff --git a/platform-enterprise_versioned_docs/version-23.2/enterprise/_templates/k8s/tower-svc.yml b/platform-enterprise_versioned_docs/version-23.2/enterprise/_templates/k8s/tower-svc.yml index cff74e7af..a91803ace 100644 --- a/platform-enterprise_versioned_docs/version-23.2/enterprise/_templates/k8s/tower-svc.yml +++ b/platform-enterprise_versioned_docs/version-23.2/enterprise/_templates/k8s/tower-svc.yml @@ -98,6 +98,26 @@ spec: selector: app: backend --- +# +# Backend API Service (Optional) +# +# This service exposes the backend API directly if you wish to have a separate +# API endpoint (e.g., api.cloud.seqera.io) distinct from the main frontend. +# +# When to use this: +# - You want a dedicated subdomain for API/CLI access (e.g., api.yourcompany.com) +# - You need to separate API traffic from web UI traffic +# +# Required configuration when enabled: +# - Configure appropriate ingress rules for the API subdomain +# - Ensure your DNS points the API subdomain to this service +# +# Note: This service is optional. Most deployments do not need this unless +# you intentionally want to expose the backend API via a dedicated subdomain. +# If not needed, you can remove this service to simplify your deployment and +# avoid potential routing conflicts with the frontend's wildcard setup. +# +--- apiVersion: v1 kind: Service metadata: diff --git a/platform-enterprise_versioned_docs/version-23.3/enterprise/_templates/k8s/tower-svc.yml b/platform-enterprise_versioned_docs/version-23.3/enterprise/_templates/k8s/tower-svc.yml index f5000eb74..f568c2403 100644 --- a/platform-enterprise_versioned_docs/version-23.3/enterprise/_templates/k8s/tower-svc.yml +++ b/platform-enterprise_versioned_docs/version-23.3/enterprise/_templates/k8s/tower-svc.yml @@ -98,6 +98,26 @@ spec: selector: app: backend --- +# +# Backend API Service (Optional) +# +# This service exposes the backend API directly if you wish to have a separate +# API endpoint (e.g., api.cloud.seqera.io) distinct from the main frontend. +# +# When to use this: +# - You want a dedicated subdomain for API/CLI access (e.g., api.yourcompany.com) +# - You need to separate API traffic from web UI traffic +# +# Required configuration when enabled: +# - Configure appropriate ingress rules for the API subdomain +# - Ensure your DNS points the API subdomain to this service +# +# Note: This service is optional. Most deployments do not need this unless +# you intentionally want to expose the backend API via a dedicated subdomain. +# If not needed, you can remove this service to simplify your deployment and +# avoid potential routing conflicts with the frontend's wildcard setup. +# +--- apiVersion: v1 kind: Service metadata: diff --git a/platform-enterprise_versioned_docs/version-23.4/enterprise/_templates/k8s/tower-svc.yml b/platform-enterprise_versioned_docs/version-23.4/enterprise/_templates/k8s/tower-svc.yml index 9913d0ecc..f99852225 100644 --- a/platform-enterprise_versioned_docs/version-23.4/enterprise/_templates/k8s/tower-svc.yml +++ b/platform-enterprise_versioned_docs/version-23.4/enterprise/_templates/k8s/tower-svc.yml @@ -98,6 +98,26 @@ spec: selector: app: backend --- +# +# Backend API Service (Optional) +# +# This service exposes the backend API directly if you wish to have a separate +# API endpoint (e.g., api.cloud.seqera.io) distinct from the main frontend. +# +# When to use this: +# - You want a dedicated subdomain for API/CLI access (e.g., api.yourcompany.com) +# - You need to separate API traffic from web UI traffic +# +# Required configuration when enabled: +# - Configure appropriate ingress rules for the API subdomain +# - Ensure your DNS points the API subdomain to this service +# +# Note: This service is optional. Most deployments do not need this unless +# you intentionally want to expose the backend API via a dedicated subdomain. +# If not needed, you can remove this service to simplify your deployment and +# avoid potential routing conflicts with the frontend's wildcard setup. +# +--- apiVersion: v1 kind: Service metadata: diff --git a/platform-enterprise_versioned_docs/version-24.1/enterprise/_templates/k8s/tower-svc.yml b/platform-enterprise_versioned_docs/version-24.1/enterprise/_templates/k8s/tower-svc.yml index 7aeb36d78..41ba861a0 100644 --- a/platform-enterprise_versioned_docs/version-24.1/enterprise/_templates/k8s/tower-svc.yml +++ b/platform-enterprise_versioned_docs/version-24.1/enterprise/_templates/k8s/tower-svc.yml @@ -111,6 +111,26 @@ spec: selector: app: backend --- +# +# Backend API Service (Optional) +# +# This service exposes the backend API directly if you wish to have a separate +# API endpoint (e.g., api.cloud.seqera.io) distinct from the main frontend. +# +# When to use this: +# - You want a dedicated subdomain for API/CLI access (e.g., api.yourcompany.com) +# - You need to separate API traffic from web UI traffic +# +# Required configuration when enabled: +# - Configure appropriate ingress rules for the API subdomain +# - Ensure your DNS points the API subdomain to this service +# +# Note: This service is optional. Most deployments do not need this unless +# you intentionally want to expose the backend API via a dedicated subdomain. +# If not needed, you can remove this service to simplify your deployment and +# avoid potential routing conflicts with the frontend's wildcard setup. +# +--- apiVersion: v1 kind: Service metadata: diff --git a/platform-enterprise_versioned_docs/version-24.2/enterprise/_templates/k8s/tower-svc.yml b/platform-enterprise_versioned_docs/version-24.2/enterprise/_templates/k8s/tower-svc.yml index baafe9d20..a4bf47752 100644 --- a/platform-enterprise_versioned_docs/version-24.2/enterprise/_templates/k8s/tower-svc.yml +++ b/platform-enterprise_versioned_docs/version-24.2/enterprise/_templates/k8s/tower-svc.yml @@ -111,6 +111,26 @@ spec: selector: app: backend --- +# +# Backend API Service (Optional) +# +# This service exposes the backend API directly if you wish to have a separate +# API endpoint (e.g., api.cloud.seqera.io) distinct from the main frontend. +# +# When to use this: +# - You want a dedicated subdomain for API/CLI access (e.g., api.yourcompany.com) +# - You need to separate API traffic from web UI traffic +# +# Required configuration when enabled: +# - Configure appropriate ingress rules for the API subdomain +# - Ensure your DNS points the API subdomain to this service +# +# Note: This service is optional. Most deployments do not need this unless +# you intentionally want to expose the backend API via a dedicated subdomain. +# If not needed, you can remove this service to simplify your deployment and +# avoid potential routing conflicts with the frontend's wildcard setup. +# +--- apiVersion: v1 kind: Service metadata: diff --git a/platform-enterprise_versioned_docs/version-25.1/enterprise/_templates/k8s/tower-svc.yml b/platform-enterprise_versioned_docs/version-25.1/enterprise/_templates/k8s/tower-svc.yml index 120222614..3de8a41e5 100644 --- a/platform-enterprise_versioned_docs/version-25.1/enterprise/_templates/k8s/tower-svc.yml +++ b/platform-enterprise_versioned_docs/version-25.1/enterprise/_templates/k8s/tower-svc.yml @@ -111,6 +111,26 @@ spec: selector: app: backend --- +# +# Backend API Service (Optional) +# +# This service exposes the backend API directly if you wish to have a separate +# API endpoint (e.g., api.cloud.seqera.io) distinct from the main frontend. +# +# When to use this: +# - You want a dedicated subdomain for API/CLI access (e.g., api.yourcompany.com) +# - You need to separate API traffic from web UI traffic +# +# Required configuration when enabled: +# - Configure appropriate ingress rules for the API subdomain +# - Ensure your DNS points the API subdomain to this service +# +# Note: This service is optional. Most deployments do not need this unless +# you intentionally want to expose the backend API via a dedicated subdomain. +# If not needed, you can remove this service to simplify your deployment and +# avoid potential routing conflicts with the frontend's wildcard setup. +# +--- apiVersion: v1 kind: Service metadata: diff --git a/platform-enterprise_versioned_docs/version-25.2/enterprise/_templates/k8s/tower-svc.yml b/platform-enterprise_versioned_docs/version-25.2/enterprise/_templates/k8s/tower-svc.yml index e13cb31a0..ff6e93f7c 100644 --- a/platform-enterprise_versioned_docs/version-25.2/enterprise/_templates/k8s/tower-svc.yml +++ b/platform-enterprise_versioned_docs/version-25.2/enterprise/_templates/k8s/tower-svc.yml @@ -111,6 +111,26 @@ spec: selector: app: backend --- +# +# Backend API Service (Optional) +# +# This service exposes the backend API directly if you wish to have a separate +# API endpoint (e.g., api.cloud.seqera.io) distinct from the main frontend. +# +# When to use this: +# - You want a dedicated subdomain for API/CLI access (e.g., api.yourcompany.com) +# - You need to separate API traffic from web UI traffic +# +# Required configuration when enabled: +# - Configure appropriate ingress rules for the API subdomain +# - Ensure your DNS points the API subdomain to this service +# +# Note: This service is optional. Most deployments do not need this unless +# you intentionally want to expose the backend API via a dedicated subdomain. +# If not needed, you can remove this service to simplify your deployment and +# avoid potential routing conflicts with the frontend's wildcard setup. +# +--- apiVersion: v1 kind: Service metadata: