chore: Update che.properties defaults (#960)

Signed-off-by: Anatolii Bazko <abazko@redhat.com>

Author: tolusha

assembly/assembly-wsmaster-war/src/main/webapp/WEB-INF/classes/che/che.properties

@@ -1,5 +1,5 @@
 #
-# Copyright (c) 2012-2024 Red Hat, Inc.
+# Copyright (c) 2012-2026 Red Hat, Inc.
 # This program and the accompanying materials are made
 # available under the terms of the Eclipse Public License 2.0
 # which is available at https://www.eclipse.org/legal/epl-2.0/
@@ -95,7 +95,7 @@ che.workspace.startup_debug_log_limit_bytes=10485760
 # This property is set by the {prod-short} Operator if it also installed the support for DevWorkspaces.
 # This property is used to advertise this fact to the {prod-short} dashboard.
 # It doesn't make sense to change the value of this property manually.
-che.devworkspaces.enabled=false
+che.devworkspaces.enabled=true
 
 ### Authentication parameters
 
@@ -250,20 +250,20 @@ db.schema.flyway.scripts.locations=classpath:che-schema
 che.infra.kubernetes.master_url=
 
 # Boolean to configure Kubernetes Client to use trusted certificates.
-che.infra.kubernetes.trust_certs=false
+che.infra.kubernetes.trust_certs=true
 
 # Kubernetes cluster domain. If not set, svc names doesn't contain information about the cluster domain.
 che.infra.kubernetes.cluster_domain=NULL
 
 # Defines how servers are exposed to the world in Kubernetes infra.
 # Options include: `default-host`, `multi-host`, `single-host`.
-che.infra.kubernetes.server_strategy=multi-host
+che.infra.kubernetes.server_strategy=single-host
 
 # Defines the way in which the workspace plug-ins and editors are exposed in the single-host mode.
 # Supported exposures:
 # `native`:: Exposes servers using Kubernetes Ingresses. Works only on Kubernetes.
 # `gateway`:: Exposes servers using reverse-proxy gateway.
-che.infra.kubernetes.singlehost.workspace.exposure=native
+che.infra.kubernetes.singlehost.workspace.exposure=gateway
 
 # Defines the way to expose devfile endpoints as end-user's applications, in single-host server strategy.
 # They can either follow the single-host strategy and be exposed on subpaths, or they can be exposed on subdomains.
@@ -401,7 +401,7 @@ che.infra.kubernetes.pod.termination_grace_period_sec=0
 
 # Creates Ingresses with Transport Layer Security (TLS) enabled.
 # In OpenShift infrastructure, Routes are TLS-enabled.
-che.infra.kubernetes.tls_enabled=false
+che.infra.kubernetes.tls_enabled=true
 
 # The name of a secret that should be used when creating workspace Ingresses with TLS.
 # This property is ignored by OpenShift infrastructure.
@@ -503,7 +503,7 @@ che.workspace.plugin_broker.wait_timeout_min=3
 # Workspace plug-in registry endpoint. Should be a valid HTTP URL.
 # Example: `++http://che-plugin-registry-eclipse-che.192.168.65.2.nip.io++`
 # In case the {prod-short} plug-in registry isn't needed, use the value 'NULL'.
-che.workspace.plugin_registry_url=https://che-plugin-registry.prod-preview.openshift.io/v3
+che.workspace.plugin_registry_url=NULL
 
 # Workspace plug-in registry internal endpoint. Should be a valid HTTP URL.
 # Example: `++http://devfile-registry.che.svc.cluster.local:8080++`
@@ -513,7 +513,7 @@ che.workspace.plugin_registry_internal_url=NULL
 # Devfile registry endpoint. Should be a valid HTTP URL.
 # Example: `++http://che-devfile-registry-eclipse-che.192.168.65.2.nip.io++`
 # In case the {prod-short} plug-in registry isn't needed, use the value 'NULL'.
-che.workspace.devfile_registry_url=https://che-devfile-registry.prod-preview.openshift.io/
+che.workspace.devfile_registry_url=NULL
 
 # Devfile registry "internal" endpoint. Should be a valid HTTP URL.
 # Example: `++http://plugin-registry.che.svc.cluster.local:8080++`