chore: remove optional backend-api service from tower-svc.yml default manifest

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:

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:

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:

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:

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:

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:

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:

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:

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:

platform-enterprise_versioned_docs/version-25.3/enterprise/_templates/k8s/tower-svc.yml

@@ -95,7 +95,7 @@ spec:
           ports:
             - containerPort: 80
       restartPolicy: Always
----
+
 # Services
 apiVersion: v1
 kind: Service
@@ -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: