@leverege/build-tools 2.23.4 → 2.23.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leverege/build-tools",
-  "version": "2.23.4",
+  "version": "2.23.5",
   "description": "A collection of build / support tools for Leverege developers",
   "main": "index.js",
   "repository": {
@@ -63,7 +63,7 @@
     "parse-gitignore": "^2.0.0",
     "readline-sync": "^1.4.10",
     "semver": "^7.3.8",
-    "simple-git": "^3.15.1",
+    "simple-git": "^3.16.0",
     "zx": "^7.1.1"
   },
   "devDependencies": {

package/src/system-charts/cert-manager.hup

@@ -1,5 +1,37 @@
 #!/bin/bash
 #
-# cert-manager is skipped for now - we may not really need it
+# cert-manager may be skipped for now?
 #
-skipInstalling cert-manager
+skipInstalling cert-manager && exit 0
+#
+addHelmRepo jetstack https://charts.jetstack.io
+[ -z "$CERT_MANAGER_HELM_CHART" ] && CERT_MANAGER_HELM_CHART="v1.10"
+helm upgrade --install cert-manager jetstack/cert-manager \
+  --namespace cert-manager --set installCRDs=true \
+  --version $CERT_MANAGER_HELM_CHART
+
+cat<<DELAY
+
+  `color y "20 second delay to allow cert-manager to stabilize before proceeding...\n"`
+
+DELAY
+
+sleep 20
+kubectl -n cert-manager apply -f cert-manager
+
+if [[ $? -eq 1 ]];
+then
+
+  `color y "***WARNING: cert-manager components still coming up"`
+
+  Try rerunning this apply again in 30 seconds:
+  `color g "kubectl -n cert-manager apply -f cert-manager"`
+fi
+
+cat<<HINTS
+
+  fetch certs: `color g "kubectl -n cert-manager get certificate"`
+  check certs: `color g "kubectl -n cert-manager describe certificate"`
+
+HINTS
+removeHelmRepo jetstack

package/src/system-charts/velero-local.yaml

@@ -1,3 +1,4 @@
+#
 # Backup schedules to create.
 #
 schedules:
@@ -23,6 +24,17 @@ schedules:
           release: "timescale-db"
           app: "postgresql"
 
+  mysql:
+    disabled: true
+    schedule: "0 4 * * *"
+    template:
+      ttl: "720h"
+      snapshotVolumes: true
+      labelSelector:
+        matchLabels:
+          release: "mysql"
+          app: "mysql"
+
   redis:
     disabled: true
     schedule: "*/30 * * * *"
@@ -98,8 +110,29 @@ serviceAccount:
     create: false
     name: velero
 
-# Info about the secret to be used by the Velero deployment, which
-# should contain credentials for the cloud provider IAM account you've
-# set up for Velero.
+# Workload Identity Federation (WIF) uses service accounts and IAM roles to
+# define a service's permissions - the useSecret setting will be set to false
+# for WIF enabled clusters.
+#
+# In order to use velero in a non WIF legacy cluster, ensure the k8s context
+# by running from the root of the git repository:
+#    $ overwhelm
+#
+# Create and download a key file for the existing velero SA:
+#    $ gcloud iam service-accounts keys create velero-credentials \
+#           --iam-account velero@<project id>.iam.gserviceaccount.com
+#
+# Create the velero namespace if it does not already exist:
+#    $ kubectl create ns velero
+#
+# Inject the secret into the cluster's velero namespace:
+#    $ kubectl create secret generic velero-credentials  \
+#           --namespace velero --from-file cloud=velero-credentials
+#      
+# Clean up the secret now that it is injected:
+#    $ rm velero-credentials
+#
+# Comment out the useSecret - uncomment existingSecret - helmup velero
 credentials:
-  useSecret: false
+  useSecret: false # comment out for non WIF
+# existingSecret: velero-credentials # uncomment for non WIF