feat: add vui

argocd-apps/applicationset.yaml

@@ -39,6 +39,7 @@ spec:
           - name: tailscale-operator
           - name: vaultwarden
           - name: velero
+          - name: velero-ui
 
   template:
     metadata:

k8s-apps/velero-ui/Chart.yaml

@@ -0,0 +1,9 @@
+apiVersion: v2
+name: velero-ui
+description: A UI for Velero
+type: application
+version: 0.1.0
+dependencies:
+  - name: vui
+    repository: https://seriohub.github.io/velero-helm/
+    version: 0.1.15

k8s-apps/velero-ui/templates/es.yaml

@@ -0,0 +1,25 @@
+apiVersion: external-secrets.io/v1beta1
+kind: ExternalSecret
+metadata:
+  name: backblaze-credentials
+spec:
+  secretStoreRef:
+    kind: ClusterSecretStore
+    name: gitlab-secret-store
+  target:
+    name: backblaze-credentials
+    creationPolicy: Owner
+    # template:
+    #   engineVersion: v2
+    #   data:
+    #     config: |
+    #       [default]
+    #       aws_access_key_id = "{{"{{ .access_key }}"}}"
+    #       aws_secret_access_key = "{{"{{ .secret_key }}"}}"
+  data:
+    - secretKey: AWS_ACCESS_KEY_ID
+      remoteRef:
+        key: velero_backblaze_access_key_id
+    - secretKey: AWS_SECRET_ACCESS_KEY
+      remoteRef:
+        key: velero_backblaze_secret_access_key

k8s-apps/velero-ui/values.yaml

@@ -0,0 +1,101 @@
+vui:
+  #
+  # Global
+  #
+  global:
+    veleroNamespace: velero
+    # kubernetesClusterDomain: my-cluster
+    # agentMode: false
+    # clusterName: <your-cluster-name>
+
+  #
+  # API Config
+  #
+  apiConfig:
+    # To generate a fixed secure random secret key use the command: openssl rand -hex 32
+    # securityTokenKey:
+    #
+    existingSecret: backblaze-credentials
+    # debugLevel: debug
+    veleroCliVersion: v1.12.2
+    # apiTokenExpirationMin: "30"
+    # apiTokenRefreshExpirationDays: "7"
+    storage:
+      enabled: false
+      storageClassName: <your-storage-class-name>
+
+  #
+  # You can use nodeport or ingress according to your needs
+  #
+  #
+  # Nodeport
+  #
+  uiNp:
+    enabled: false
+    ip: "10.10.0.100" # any ip address of your cluster
+    apiPort: "30001"
+    uiPort: "30002"
+  #
+  # Ingress
+  #
+  uiIngress:
+    enabled: true
+    ingressClassName: nginx
+    metadata:
+      annotations:
+        cert-manager.io/cluster-issuer: "letsencrypt"
+        external-dns.alpha.kubernetes.io/target: "home.terence.cloud"
+    spec:
+      tls:
+        - hosts:
+            - velero.terence.cloud
+          secretName: velero-ui-tls
+
+  #
+  # Watchdog Cron
+  #
+  report:
+    schedule: 0 8 * * *
+
+  #
+  # Watchdog Daemon
+  #
+  watchdogConfig:
+    # config
+    k8SInclusterMode: "True"
+    # k8sVeleroNamespace: "velero"
+    processClusterName: homelab
+    # processCycleSec: 300
+    # expiresDaysWarning: 29
+    notificationSkipCompleted: "False"
+    # notificationSkipInProgress: "True"
+    # notificationSkipRemoved: "True"
+    # notificationSkipDeleting: "True"
+
+    # email
+    emailEnable: "False"
+    emailAccount: <your-email>
+    emailPassword: <your-password>
+    emailRecipients: <email-recipents-comma-saparted>
+    emailSmtpPort: <smtp-port>
+    emailSmtpServer: <smtp-server>
+
+    # slack
+    slackEnable: "False"
+    slackChannel: <channel-id>
+    slackToken: <token>
+
+    # TODO: telegram
+    telegramEnable: "False"
+    telegramChatId: "<telegram-chat-id>"
+    telegramToken: "<telegram-token>"
+
+  #
+  # uiConfig
+  # you can enable an experimental function to add a second cluster to the login screen
+  #
+  # uiConfig:
+  # experimental: true
+  # exNextPublicVeleroApiName2: "your-cluster-name-2"
+  # exNextPublicVeleroApiUrl2: "https://your-url-api-2/api"
+  # exNextPublicVeleroApiWs2: "wss://your-url-api-2"