From 023ebfee5d4f351e24ff16dc9bbe3a04e505c8ca Mon Sep 17 00:00:00 2001
From: Nikholas Pcenicni <82239765+nikpcenicni@users.noreply.github.com>
Date: Sun, 29 Mar 2026 02:03:57 -0400
Subject: [PATCH] Enhance Eclipse Che configuration in checluster.yaml by
 adding externalTLSConfig for secure workspace subdomains. This change ensures
 cert-manager can issue TLS certificates, preventing issues with unavailable
 servers when opening workspaces.

---
 clusters/noble/apps/eclipse-che/checluster.yaml | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/clusters/noble/apps/eclipse-che/checluster.yaml b/clusters/noble/apps/eclipse-che/checluster.yaml
index 627fd00..2b8cc71 100644
--- a/clusters/noble/apps/eclipse-che/checluster.yaml
+++ b/clusters/noble/apps/eclipse-che/checluster.yaml
@@ -1,11 +1,21 @@
 # Eclipse Che instance — applied after **che-operator** is running (sync wave 2).
 # Edit **hostname** / **domain** if your ingress DNS differs from the noble lab pattern.
+#
+# **devEnvironments.networking.externalTLSConfig** — required with cert-manager for **workspace** subdomains.
+# Without it, Che creates secure workspace Ingresses with TLS hosts but **no secretName**, so cert-manager
+# never issues certs and the dashboard often shows **no available server** when opening a workspace.
 apiVersion: org.eclipse.che/v2
 kind: CheCluster
 metadata:
   name: eclipse-che
   namespace: eclipse-che
 spec:
+  devEnvironments:
+    networking:
+      externalTLSConfig:
+        enabled: true
+        annotations:
+          cert-manager.io/cluster-issuer: letsencrypt-prod
   networking:
     domain: apps.noble.lab.pcenicni.dev
     hostname: che.apps.noble.lab.pcenicni.dev