Merge pull request #374 from sighupio/feat/release-v1.29.7

Feat: backport 1.31.1 for release v1.29.7

Author: ralgozino

.drone.yml

@@ -59,7 +59,7 @@ steps:
   #     - schema-check
 
   - name: test-schema
-    image: quay.io/sighup/e2e-testing:1.1.0_1.30.5_3.10.0_4.33.3
+    image: quay.io/sighup/e2e-testing:2.24.17_1.1.0_3.12.0_1.29.1_5.6.0_4.33.3
     pull: always
     depends_on:
       - license-check
@@ -72,15 +72,15 @@ steps:
       - bats -t tests/schema.sh
 
   - name: render
-    image: quay.io/sighup/e2e-testing:1.1.0_1.30.5_3.10.0_4.33.3
+    image: quay.io/sighup/e2e-testing:2.24.17_1.1.0_3.12.0_1.29.1_5.6.0_4.33.3
     pull: always
     depends_on:
       - license-check
       - schema-check
     environment:
       NETRC_FILE:
         from_secret: NETRC_FILE
-      FURYCTL_VERSION: v0.31.0
+      FURYCTL_VERSION: v0.32.0-rc.3
       FURYCTL_CONFIG: tests/e2e/kfddistribution/furyctl-init-cluster.yaml
       FURYCTL_DISTRO_LOCATION: ./
       FURYCTL_OUTDIR: ./
@@ -129,7 +129,7 @@ trigger:
 
 steps:
   - name: create Kind cluster
-    image: quay.io/sighup/dind-kind-kubectl-kustomize:0.24.0_1.30.5_3.10.0
+    image: quay.io/sighup/dind-kind-kubectl-kustomize:0.27.0_1.29.1_5.6.0
     pull: always
     volumes:
       - name: dockersock
@@ -162,15 +162,15 @@ steps:
       - kind get kubeconfig --name $${CLUSTER_NAME} > $${KUBECONFIG}
 
   - name: e2e-kfddistribution
-    image: quay.io/sighup/e2e-testing:1.1.0_1.30.5_3.10.0_4.33.3
+    image: quay.io/sighup/e2e-testing:2.24.17_1.1.0_3.12.0_1.29.1_5.6.0_4.33.3
     pull: always
     # we need to use host network to access Kind API port that is listening on the worker's loopback
     # beacuse we mount the host's Docker socket to run Kind.
     network_mode: host
     environment:
       CLUSTER_NAME: ${DRONE_REPO_NAME}-${DRONE_BUILD_NUMBER}
       KUBECONFIG: /drone/src/kubeconfig
-      FURYCTL_VERSION: v0.31.0
+      FURYCTL_VERSION: v0.32.0-rc.3
     depends_on: [create Kind cluster]
     commands:
       - export KUBECONFIG=/drone/src/kubeconfig
@@ -188,7 +188,7 @@ steps:
       - tests/e2e-kfddistribution.sh
 
   - name: delete-kind-cluster
-    image: quay.io/sighup/dind-kind-kubectl-kustomize:0.24.0_1.30.5_3.10.0
+    image: quay.io/sighup/dind-kind-kubectl-kustomize:0.27.0_1.29.1_5.6.0
     volumes:
       - name: dockersock
         path: /var/run/docker.sock
@@ -209,7 +209,7 @@ volumes:
     host:
       path: /var/run/docker.sock
 ---
-name: e2e-kubernetes-1.29.5-to-1.29.6
+name: e2e-kubernetes-1.29.6-to-1.29.7
 kind: pipeline
 type: docker
 
@@ -233,7 +233,7 @@ trigger:
 
 steps:
   - name: create Kind cluster
-    image: quay.io/sighup/dind-kind-kubectl-kustomize:0.24.0_1.30.5_3.10.0
+    image: quay.io/sighup/dind-kind-kubectl-kustomize:0.27.0_1.29.1_5.6.0
     pull: always
     volumes:
       - name: dockersock
@@ -266,15 +266,15 @@ steps:
       - kind get kubeconfig --name $${CLUSTER_NAME} > $${KUBECONFIG}
 
   - name: e2e-kfddistribution
-    image: quay.io/sighup/e2e-testing:1.1.0_1.30.5_3.10.0_4.33.3
+    image: quay.io/sighup/e2e-testing:2.24.17_1.1.0_3.12.0_1.29.1_5.6.0_4.33.3
     pull: always
     # we need to use host network to access Kind API port that is listening on the worker's loopback
     # beacuse we mount the host's Docker socket to run Kind.
     network_mode: host
     environment:
       CLUSTER_NAME: ${DRONE_REPO_NAME}-${DRONE_BUILD_NUMBER}-upgrades
       KUBECONFIG: /drone/src/kubeconfig-upgrades
-      FURYCTL_VERSION: v0.31.0
+      FURYCTL_VERSION: v0.32.0-rc.3
     depends_on: [create Kind cluster]
     commands:
       - export KUBECONFIG=/drone/src/kubeconfig-upgrades
@@ -292,7 +292,7 @@ steps:
       - tests/e2e-kfddistribution-upgrades.sh
 
   - name: delete-kind-cluster
-    image: quay.io/sighup/dind-kind-kubectl-kustomize:0.24.0_1.30.5_3.10.0
+    image: quay.io/sighup/dind-kind-kubectl-kustomize:0.27.0_1.29.1_5.6.0
     volumes:
       - name: dockersock
         path: /var/run/docker.sock
@@ -319,7 +319,7 @@ type: docker
 
 depends_on:
   - e2e-kubernetes-1.29
-  - e2e-kubernetes-1.29.5-to-1.29.6
+  - e2e-kubernetes-1.29.6-to-1.29.7
 
 platform:
   os: linux

README.md

@@ -1,6 +1,6 @@
 # EKSCluster - EKS Cluster Schema
 
-This document explains the full schema for the `kind: EKSCluster` for the `furyctl.yaml` file used by `furyctl`. This configuration file will be used to deploy a Kubernetes Fury Cluster deployed through AWS's Elastic Kubernetes Service.
+This document explains the full schema for the `kind: EKSCluster` for the `furyctl.yaml` file used by `furyctl`. This configuration file will be used to deploy a SIGHUP Distribution cluster deployed through AWS's Elastic Kubernetes Service.
 
 An example configuration file can be created by running the following command:
 

banners/ekscluster.md

@@ -1,6 +1,6 @@
 # KFDDistribution - Distribution Only Cluster Schema
 
-This document explains the full schema for the `kind: KFDDistribution` for the `furyctl.yaml` file used by `furyctl`. This configuration file will be used to deploy the Kubernetes Fury Distribution modules on top of an existing Kubernetes cluster.
+This document explains the full schema for the `kind: KFDDistribution` for the `furyctl.yaml` file used by `furyctl`. This configuration file will be used to deploy the SIGHUP Distribution modules on top of an existing Kubernetes cluster.
 
 An example configuration file can be created by running the following command:
 

banners/kfddistribution.md

@@ -1,6 +1,6 @@
-# OnPremises - KFD On Premises Cluster Schema
+# OnPremises - SD On Premises Cluster Schema
 
-This document explains the full schema for the `kind: OnPremises` for the `furyctl.yaml` file used by `furyctl`. This configuration file will be used to deploy the Kubernetes Fury Distribution modules and cluster on premises.
+This document explains the full schema for the `kind: OnPremises` for the `furyctl.yaml` file used by `furyctl`. This configuration file will be used to deploy the SIGHUP Distribution modules and cluster on premises.
 
 An example configuration file can be created by running the following command:
 

banners/onpremises.md

@@ -237,6 +237,8 @@ data:
       overrides:
         nodeSelector: null
         tolerations: null
+      etcdBackup:
+        type: "none"
       # the standard configuration for velero on the dr module
       velero:
         backend: minio

defaults/ekscluster-kfd-v1alpha2.yaml

@@ -229,6 +229,11 @@ data:
       overrides:
         nodeSelector: null
         tolerations: null
+      # etcdBackup isn't supported in the KFDDistribution provider.
+      # It is defined here only because otherwise the template engine
+      # breaks.
+      etcdBackup:
+        type: "none"
       # the standard configuration for velero on the dr module
       velero:
         backend: minio

defaults/kfddistribution-kfd-v1alpha2.yaml

@@ -229,6 +229,18 @@ data:
       overrides:
         nodeSelector: null
         tolerations: null
+      etcdBackup:
+        type: "none"
+        pvc:
+          schedule: "0 1 * * *"
+          retentionTime: 10d
+          size: 10G
+          storageClass: null
+          accessModes: ["ReadWriteOnce"]
+        s3:
+          schedule: "0 1 * * *"
+          retentionTime: 10d
+          insecure: false
       # the standard configuration for velero on the dr module
       velero:
         backend: minio