From 5495aecd5232ba7b00a440743e7b3550e4497e7b Mon Sep 17 00:00:00 2001 From: Mark P Date: Wed, 24 Sep 2025 15:53:39 -0400 Subject: [PATCH 1/2] Removed backend-api from tower-svc.yml manifest --- .../enterprise/_templates/k8s/tower-svc.yml | 13 ------------- .../enterprise/_templates/k8s/tower-svc.yml | 13 ------------- .../enterprise/_templates/k8s/tower-svc.yml | 13 ------------- .../enterprise/_templates/k8s/tower-svc.yml | 13 ------------- .../enterprise/_templates/k8s/tower-svc.yml | 13 ------------- .../enterprise/_templates/k8s/tower-svc.yml | 13 ------------- .../enterprise/_templates/k8s/tower-svc.yml | 13 ------------- .../enterprise/_templates/k8s/tower-svc.yml | 13 ------------- .../enterprise/_templates/k8s/tower-svc.yml | 13 ------------- 9 files changed, 117 deletions(-) diff --git a/platform-enterprise_docs/enterprise/_templates/k8s/tower-svc.yml b/platform-enterprise_docs/enterprise/_templates/k8s/tower-svc.yml index e908107fd..de47bf7ff 100644 --- a/platform-enterprise_docs/enterprise/_templates/k8s/tower-svc.yml +++ b/platform-enterprise_docs/enterprise/_templates/k8s/tower-svc.yml @@ -110,19 +110,6 @@ spec: --- apiVersion: v1 kind: Service -metadata: - name: backend-api -spec: - ports: - - port: 8080 - targetPort: 8080 - protocol: TCP - type: NodePort - selector: - app: backend ---- -apiVersion: v1 -kind: Service metadata: name: frontend spec: 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..9c8c2014e 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 @@ -100,19 +100,6 @@ spec: --- apiVersion: v1 kind: Service -metadata: - name: backend-api -spec: - ports: - - port: 8080 - targetPort: 8080 - protocol: TCP - type: NodePort - selector: - app: backend ---- -apiVersion: v1 -kind: Service metadata: name: frontend spec: 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..9c8c2014e 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 @@ -100,19 +100,6 @@ spec: --- apiVersion: v1 kind: Service -metadata: - name: backend-api -spec: - ports: - - port: 8080 - targetPort: 8080 - protocol: TCP - type: NodePort - selector: - app: backend ---- -apiVersion: v1 -kind: Service metadata: name: frontend spec: 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..c7e166cc6 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 @@ -100,19 +100,6 @@ spec: --- apiVersion: v1 kind: Service -metadata: - name: backend-api -spec: - ports: - - port: 8080 - targetPort: 8080 - protocol: TCP - type: NodePort - selector: - app: backend ---- -apiVersion: v1 -kind: Service metadata: name: frontend spec: 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..b16c3004d 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 @@ -100,19 +100,6 @@ spec: --- apiVersion: v1 kind: Service -metadata: - name: backend-api -spec: - ports: - - port: 8080 - targetPort: 8080 - protocol: TCP - type: NodePort - selector: - app: backend ---- -apiVersion: v1 -kind: Service metadata: name: frontend spec: 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 7d0a96307..1ef54ac5b 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 @@ -110,19 +110,6 @@ spec: --- apiVersion: v1 kind: Service -metadata: - name: backend-api -spec: - ports: - - port: 8080 - targetPort: 8080 - protocol: TCP - type: NodePort - selector: - app: backend ---- -apiVersion: v1 -kind: Service metadata: name: frontend spec: 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 2929fbed6..b507f103c 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 @@ -110,19 +110,6 @@ spec: --- apiVersion: v1 kind: Service -metadata: - name: backend-api -spec: - ports: - - port: 8080 - targetPort: 8080 - protocol: TCP - type: NodePort - selector: - app: backend ---- -apiVersion: v1 -kind: Service metadata: name: frontend spec: 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 48f9ff111..c021f7ff7 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 @@ -110,19 +110,6 @@ spec: --- apiVersion: v1 kind: Service -metadata: - name: backend-api -spec: - ports: - - port: 8080 - targetPort: 8080 - protocol: TCP - type: NodePort - selector: - app: backend ---- -apiVersion: v1 -kind: Service metadata: name: frontend spec: 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 e908107fd..de47bf7ff 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 @@ -110,19 +110,6 @@ spec: --- apiVersion: v1 kind: Service -metadata: - name: backend-api -spec: - ports: - - port: 8080 - targetPort: 8080 - protocol: TCP - type: NodePort - selector: - app: backend ---- -apiVersion: v1 -kind: Service metadata: name: frontend spec: From fb5549b295becc87020ea516dab5ded527076661 Mon Sep 17 00:00:00 2001 From: Mark P Date: Wed, 3 Dec 2025 10:56:03 -0500 Subject: [PATCH 2/2] docs: reverted the backend-api and added warning comments --- .../enterprise/_templates/k8s/tower-svc.yml | 33 +++++++++++++++++++ .../enterprise/_templates/k8s/tower-svc.yml | 33 +++++++++++++++++++ .../enterprise/_templates/k8s/tower-svc.yml | 33 +++++++++++++++++++ .../enterprise/_templates/k8s/tower-svc.yml | 33 +++++++++++++++++++ .../enterprise/_templates/k8s/tower-svc.yml | 33 +++++++++++++++++++ .../enterprise/_templates/k8s/tower-svc.yml | 33 +++++++++++++++++++ .../enterprise/_templates/k8s/tower-svc.yml | 33 +++++++++++++++++++ .../enterprise/_templates/k8s/tower-svc.yml | 33 +++++++++++++++++++ .../enterprise/_templates/k8s/tower-svc.yml | 33 +++++++++++++++++++ 9 files changed, 297 insertions(+) diff --git a/platform-enterprise_docs/enterprise/_templates/k8s/tower-svc.yml b/platform-enterprise_docs/enterprise/_templates/k8s/tower-svc.yml index 5597e7683..057194e57 100644 --- a/platform-enterprise_docs/enterprise/_templates/k8s/tower-svc.yml +++ b/platform-enterprise_docs/enterprise/_templates/k8s/tower-svc.yml @@ -111,6 +111,39 @@ 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: + name: backend-api +spec: + ports: + - port: 8080 + targetPort: 8080 + protocol: TCP + type: NodePort + selector: + app: backend +--- 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 9c8c2014e..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,39 @@ 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: + name: backend-api +spec: + ports: + - port: 8080 + targetPort: 8080 + protocol: TCP + type: NodePort + selector: + app: backend +--- 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 9c8c2014e..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,39 @@ 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: + name: backend-api +spec: + ports: + - port: 8080 + targetPort: 8080 + protocol: TCP + type: NodePort + selector: + app: backend +--- 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 c7e166cc6..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,39 @@ 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: + name: backend-api +spec: + ports: + - port: 8080 + targetPort: 8080 + protocol: TCP + type: NodePort + selector: + app: backend +--- 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 b16c3004d..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,39 @@ 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: + name: backend-api +spec: + ports: + - port: 8080 + targetPort: 8080 + protocol: TCP + type: NodePort + selector: + app: backend +--- 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 997042450..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,39 @@ 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: + name: backend-api +spec: + ports: + - port: 8080 + targetPort: 8080 + protocol: TCP + type: NodePort + selector: + app: backend +--- 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 a59b1b65e..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,39 @@ 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: + name: backend-api +spec: + ports: + - port: 8080 + targetPort: 8080 + protocol: TCP + type: NodePort + selector: + app: backend +--- 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 3467c265f..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,39 @@ 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: + name: backend-api +spec: + ports: + - port: 8080 + targetPort: 8080 + protocol: TCP + type: NodePort + selector: + app: backend +--- 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 fcb3f4eef..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,39 @@ 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: + name: backend-api +spec: + ports: + - port: 8080 + targetPort: 8080 + protocol: TCP + type: NodePort + selector: + app: backend +--- apiVersion: v1 kind: Service metadata: