@leverege/build-tools 2.31.2 → 2.31.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leverege/build-tools",
-  "version": "2.31.2",
+  "version": "2.31.4",
   "description": "A collection of build / support tools for Leverege developers",
   "main": "index.js",
   "repository": {
@@ -70,9 +70,9 @@
   },
   "devDependencies": {
     "@babel/cli": "^7.21.0",
-    "@babel/core": "^7.21.3",
+    "@babel/core": "^7.21.4",
     "@leverege/babel-preset-leverege-node": "^2.0.0",
     "@leverege/eslint-config-leverege": "^3.0.1",
-    "npm": "^9.6.2"
+    "npm": "^9.6.4"
   }
 }

package/src/helm-charts/cert-manager/cert-manager-local.yaml.ovh

@@ -4,7 +4,7 @@
 apiVersion: cert-manager.io/v1
 kind: ClusterIssuer
 metadata:
-  name: letsencrypt-prd
+  name: letsencrypt
 spec:
   acme:
     # production
@@ -43,5 +43,5 @@ spec:
   dnsNames:
     - '*.OVH:<HOST>.com'
   issuerRef:
-    name: letsencrypt-prd
+    name: letsencrypt
     kind: ClusterIssuer

package/src/helm-charts/cert-manager/helmup.plugin

@@ -31,8 +31,8 @@ fi
 
 cat<<HINTS
 
-  fetch certs: `color g "kubectl -n cert-manager get certificate"`
-  check certs: `color g "kubectl -n cert-manager describe certificate"`
+  fetch certs: `color g "kubectl get certificate"`
+  check certs: `color g "kubectl describe certificate"`
 
 HINTS
 removeHelmRepo jetstack

package/src/helm-charts/{elastic-cluster → elasticsearch-cluster}/helmup.plugin

@@ -13,7 +13,7 @@ deployES() {
   printf "\n   Deploying ES cluster component: `color y "$ES_TYPE"`\n"
   helm upgrade --install $ES_TYPE elastic/elasticsearch \
     --version $ES_VERSION \
-    --values  elastic-cluster/$ES_TYPE.yaml
+    --values  elasticsearch-cluster/$ES_TYPE.yaml $HELM_WHAT
 }
 
 deployES "master"

package/src/helm-charts/prometheus/helmup.plugin

@@ -2,13 +2,11 @@
 #
 showInstalling "Prometheus"
 
-createNamespaceIfNeeded monitoring
-
 addHelmRepo prometheus-community https://prometheus-community.github.io/helm-charts
 
 [ -z "$PROMETHEUS_CHART_VERSION" ] && PROMETHEUS_CHART_VERSION="15"
 helm upgrade --install prometheus prometheus-community/prometheus \
-             --namespace monitoring \
+             --namespace monitoring --create-namespace \
              --values prometheus/values.yaml \
              --version $PROMETHEUS_CHART_VERSION $HELM_WHAT
 

package/src/helm-charts/traefik/helmup.plugin

@@ -6,7 +6,7 @@ TRAEFIK_NAMESPACE="traefik"
 
 addHelmRepo traefik https://helm.traefik.io/traefik
 
-[ -z "$TRAEFIK_CHART_VERSION" ] && TRAEFIK_CHART_VERSION="21"
+[ -z "$TRAEFIK_CHART_VERSION" ] && TRAEFIK_CHART_VERSION="22"
 helm upgrade --install traefik traefik/traefik \
              --namespace $TRAEFIK_NAMESPACE --create-namespace \
              --values  traefik/traefik-local.yaml \

package/src/helm-charts/traefik/traefik-local.yaml

@@ -1,7 +1,11 @@
-# This is the reserved static IP - see GCP -> VPC network -> IP addresses
+# The service section controls the load balancer IP address for applying
+# reserved static IPs and for creating a secondary LB for UDP traffic.
+# See the *** UDP PORTS *** section below for more info.
+#
 #service:
 #  spec:
-#    loadBalancerIP: xx.xx.xx.xx
+#    loadBalancerIP: "xx.xx.xx.xx"
+#  single: true # true by default,  set to false for UDP support
 
 deployment:
   replicas: 3
@@ -14,3 +18,37 @@ logs:
     enabled: true
     format: json
     bufferingSize: 10
+
+# Custom entry points may be added here - the first two are port definitions
+# for both unsecured and secured MQTT ports used by connect. Note that the
+# mqtts port has TLS termination performed by traefik and both ports are then
+# forwarded to one open port (1883) on the target service. The vernemq service
+# chart provides the IngressRouteTCP chart to make this happen.
+#
+#ports:
+#  mqtt:
+#    export: true
+#    port: 1883
+#    protocol: TCP
+#  mqtts:
+#    expose: true
+#    port: 8883
+#    protocol: TCP
+#
+# *** UDP PORTS ***
+# Traefik is also capable of providing UDP routes. However, since a GKE service
+# may not currently support mixed protocols on one load balancer we must split
+# the protocols across two different load balancers. k8s v1.24 supports the
+# MixedProtocolLBService feature but this is not yet GA in GKE. Setting the
+# service.single to false will enable the dual LB approach.
+#
+#service:         <-- this is just an example of how to set this
+#  single: false  <-- because this should appear at the top
+#
+# See the siren marine udp service chart ingressroute for an example of how to
+# setup a traefik IngressRouteUDP route.
+#ports:
+#  siren-udp:
+#    port: 1993
+#    expose: true
+#    protocol: UDP

package/src/helmup

@@ -25,7 +25,7 @@ PLATFORM=(
 )
 
 SYSTEM=(
-  elastic
+  elasticsearch
   redis
   postgres
   timescale-db
@@ -660,7 +660,7 @@ function doInstall() {
         bootstrapLocalSetup $SERVICE
         ;;
 
-      "elastic-cluster") # complex master/data/client ES cluster
+      "elasticsearch-cluster") # complex master/data/client ES cluster
         bootstrapLocalSetup $SERVICE
         ;;