gsdavidp/home-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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.

Browse Source
This commit is contained in:
Nikholas Pcenicni
2026-03-29 02:03:57 -04:00
parent 27fb4113eb
commit 023ebfee5d
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
clusters/noble/apps/eclipse-che/checluster.yaml
View File

@@ -1,11 +1,21 @@
# Eclipse Che instance — applied after **che-operator** is running (sync wave 2). # 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. # 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 apiVersion: org.eclipse.che/v2
kind: CheCluster kind: CheCluster
metadata: metadata:
name: eclipse-che name: eclipse-che
namespace: eclipse-che namespace: eclipse-che
spec: spec:
devEnvironments:
networking:
externalTLSConfig:
enabled: true
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
networking: networking:
domain: apps.noble.lab.pcenicni.dev domain: apps.noble.lab.pcenicni.dev
hostname: che.apps.noble.lab.pcenicni.dev hostname: che.apps.noble.lab.pcenicni.dev