Use in-cluster registry for builds and deploys; improve logging and cluster ops.

Remove external registry Ingress (repo.3fase.ir) and route Kaniko push and app pulls through the internal ClusterIP registry. Add RegistryService, ensure StorageClass and pull secrets on deploy, make Elasticsearch install/repair more resilient, and add per-cluster Deploy Elastic controls in admin UI.

Co-authored-by: Cursor <cursoragent@cursor.com>

backend/helm/cloudhost-logging/templates/elasticsearch-pvc.yaml

@@ -12,6 +12,9 @@ metadata:
 spec:
   accessModes:
     - ReadWriteOnce
+  {{- if .Values.storageClass }}
+  storageClassName: {{ .Values.storageClass | quote }}
+  {{- end }}
   resources:
     requests:
       storage: {{ .Values.storage }}

backend/helm/cloudhost-logging/templates/namespace.yaml

@@ -1,7 +0,0 @@
-apiVersion: v1
-kind: Namespace
-metadata:
-  name: {{ include "cloudhost-logging.namespace" . }}
-  labels:
-    app.kubernetes.io/managed-by: cloudhost
-    app.kubernetes.io/instance: {{ .Release.Name }}

backend/helm/cloudhost-logging/values.yaml

@@ -7,6 +7,8 @@ kibanaSystemPassword: ""
 clusterName: cloudhost-logs
 
 storage: 50Gi
+# Leave empty to use the cluster default StorageClass (e.g. local-path on k3s).
+storageClass: ""
 
 # Official Elastic images; require docker.elastic.co DNS + outbound HTTPS from nodes.
 # If pull fails with "lookup docker.elastic.co: Try again", mirror to your registry and override here.

backend/helm/cloudhost-platform/values-production.example.yaml

@@ -38,7 +38,8 @@ ingress:
 backend:
   env:
     PLATFORM_DOMAIN: apps.example.com
-    REGISTRY_PULL_URL: "10.0.0.50:30500"
+    REGISTRY_URL: registry.cloudhost-builds.svc.cluster.local:5000
+    REGISTRY_PULL_URL: registry.cloudhost-builds.svc.cluster.local:5000
 
 migrations:
   enabled: true