migrate pv provisioner to longhorn for prometheus, retain local-path for studio

Signed-off-by: wwanarif <[email protected]>

Author: wwanarif

setup-scripts/setup-genai-studio/manifests/monitoring-manifest.yaml

@@ -285,7 +285,7 @@ spec:
   resources:
     requests:
       storage: "5Gi"
-  storageClassName: local-path
+  storageClassName: longhorn
 ---
 # Source: kube-prometheus-stack/charts/grafana/templates/clusterrole.yaml
 kind: ClusterRole
@@ -1665,7 +1665,7 @@ spec:
   storage:
     volumeClaimTemplate:
       spec:
-        storageClassName: local-path
+        storageClassName: longhorn
         accessModes: ["ReadWriteOnce"]
         resources:
           requests:

setup-scripts/setup-genai-studio/playbooks/deploy-monitoring.yml

@@ -1,19 +1,19 @@
-- name: Deploy prometheus and grafana with local-path-storage
+- name: Deploy prometheus and grafana with longhorn-system
   hosts: localhost
   tasks:
-    - name: Check if local-path-storage namespace exists
-      shell: kubectl get namespace local-path-storage --ignore-not-found
+    - name: Check if longhorn-system namespace exists
+      shell: kubectl get namespace longhorn-system --ignore-not-found
       register: namespace_check
       ignore_errors: yes
       changed_when: false
 
-    - name: Install local-path-provisioner if namespace does not exist
-      shell: kubectl apply -f https://raw.githubusercontent.com/rancher/local-path-provisioner/v0.0.30/deploy/local-path-storage.yaml
+    - name: Install longhorn-system if namespace does not exist
+      shell: kubectl apply -f https://raw.githubusercontent.com/longhorn/longhorn/v1.8.0/deploy/longhorn.yaml
       when: namespace_check.stdout == ""
       register: apply_output
 
-    - name: Wait for local-path-provisioner to be ready
-      shell: kubectl wait --for=condition=Ready pod -l app=local-path-provisioner -n local-path-storage --timeout=120s
+    - name: Wait for longhorn-system to be ready
+      shell: kubectl wait --for=condition=Ready pod -l app=longhorn-manager -n longhorn-system --timeout=120s
       when: namespace_check.stdout == ""
 
     - name: Create monitoring namespace

setup-scripts/setup-genai-studio/playbooks/deploy-studio.yml

@@ -3,7 +3,21 @@
   vars_files:
     - ../vars.yml
   tasks:
-  
+    - name: Check if local-path-storage namespace exists
+      shell: kubectl get namespace local-path-storage --ignore-not-found
+      register: namespace_check
+      ignore_errors: yes
+      changed_when: false
+    
+    - name: Install local-path-provisioner if namespace does not exist
+      shell: kubectl apply -f https://raw.githubusercontent.com/rancher/local-path-provisioner/v0.0.30/deploy/local-path-storage.yaml
+      when: namespace_check.stdout == ""
+      register: apply_output
+    
+    - name: Wait for local-path-provisioner to be ready
+      shell: kubectl wait --for=condition=Ready pod -l app=local-path-provisioner -n local-path-storage --timeout=120s
+      when: namespace_check.stdout == ""
+
     - name: Check if studio namespace exists
       command: kubectl get namespace studio
       register: studio_namespace

setup-scripts/setup-genai-studio/readme.md

@@ -6,9 +6,9 @@ The genai-studio playbook script will:
 
 1. Install MySQL server on the local machine and configure the studio db user to be secured with SSL encryption.
 
-2. Deploy a customized monitoring stack based on prometheus-community/kube-prometheus-stack (which contains both Prometheus and Grafana) in the monitoring namespace with a local-path-provisioner in local-path-storage namespace, for dynamic Persistent Volumes (PVs) provisioning.
+2. Deploy a customized monitoring stack based on prometheus-community/kube-prometheus-stack (which contains both Prometheus and Grafana) in the monitoring namespace with a longhorn provisioner from longhorn-system namespace, for dynamic Persistent Volumes (PVs) provisioning.
 
-3. Deploy Keycloak, studio-backend, studio-frontend, and studio-nginx within the studio namespace. A self-signed certificate will be generated for Keycloak usage and stored as secrets within the studio namespace. Additionally, the client SSL certificates generated during the MySQL server installation process will also be stored as secrets in the studio namespace to ensure encrypted communication to the MySQL database.
+3. Deploy Keycloak, studio-backend, studio-frontend, and studio-nginx within the studio namespace. Also using local-path-provisioner for sandbox's dynamic Persistent Volumes (PVs) provisioning. A self-signed certificate will be generated for Keycloak usage and stored as secrets within the studio namespace. Additionally, the client SSL certificates generated during the MySQL server installation process will also be stored as secrets in the studio namespace to ensure encrypted communication to the MySQL database.
 
 ## Pre-requisite