Automated update for release v0.14.5

metallb · Apr 19, 2024 · 3cee8c0 · 3cee8c0
1 parent 7ebb4a2
commit 3cee8c0
Show file tree

Hide file tree

Showing 19 changed files with 40 additions and 40 deletions.
diff --git a/charts/metallb/Chart.lock b/charts/metallb/Chart.lock
@@ -1,9 +1,9 @@
 dependencies:
 - name: crds
   repository: ""
-  version: 0.14.4
+  version: 0.14.5
 - name: frr-k8s
   repository: https://metallb.github.io/frr-k8s
   version: 0.0.11
-digest: sha256:0830886dfbdb00b06f0ee45f7f4b424e3dda50ce229c0f287e944511d9e68602
-generated: "2024-04-05T09:29:47.21116601+03:00"
+digest: sha256:d427d5fe27f36681760453c22f8df5664e1d04b33bc6f495b46a6645d68b46ec
+generated: "2024-04-19T16:34:12.167710407+02:00"
diff --git a/charts/metallb/Chart.yaml b/charts/metallb/Chart.yaml
@@ -8,7 +8,7 @@ icon: https://metallb.universe.tf/images/logo/metallb-white.png
 dependencies:
 - name: crds
   condition: crds.enabled
-  version: 0.14.4
+  version: 0.14.5
 - name: frr-k8s
   repository: https://metallb.github.io/frr-k8s
   condition: frrk8s.enabled
@@ -35,10 +35,10 @@ kubeVersion: ">= 1.19.0-0"
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
 # NOTE: this value is updated by the metallb release process
 # MetalLB chart version
-version: 0.14.4
+version: 0.14.5
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # NOTE: this value is updated by the metallb release process
-appVersion: v0.14.4
+appVersion: v0.14.5
diff --git a/charts/metallb/charts/crds/Chart.yaml b/charts/metallb/charts/crds/Chart.yaml
@@ -20,10 +20,10 @@ type: application
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
 # NOTE: this value is updated by the metallb release process
-version: 0.14.4
+version: 0.14.5
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # NOTE: this value is updated by the metallb release process
-appVersion: v0.14.4
+appVersion: v0.14.5
diff --git a/config/controllers/controller.yaml b/config/controllers/controller.yaml
@@ -30,7 +30,7 @@ spec:
           value: memberlist
         - name: METALLB_DEPLOYMENT
           value: controller
-        image: quay.io/metallb/controller:v0.14.4
+        image: quay.io/metallb/controller:v0.14.5
         name: controller
         ports:
         - containerPort: 7472

diff --git a/config/controllers/speaker.yaml b/config/controllers/speaker.yaml
@@ -45,7 +45,7 @@ spec:
           value: "app=metallb,component=speaker"
         - name: METALLB_ML_SECRET_KEY_PATH
           value: "/etc/ml_secret_key"
-        image: quay.io/metallb/speaker:v0.14.4
+        image: quay.io/metallb/speaker:v0.14.5
         name: speaker
         ports:
         - containerPort: 7472

diff --git a/config/frr/speaker-patch.yaml b/config/frr/speaker-patch.yaml
@@ -38,14 +38,14 @@ spec:
               mountPath: /etc/frr
         # Copies the reloader to the shared volume between the speaker and reloader.
         - name: cp-reloader
-          image: quay.io/metallb/speaker:v0.14.4
+          image: quay.io/metallb/speaker:v0.14.5
           command: ["/bin/sh", "-c", "cp -f /frr-reloader.sh /etc/frr_reloader/"]
           volumeMounts:
             - name: reloader
               mountPath: /etc/frr_reloader
         # Copies the metrics exporter
         - name: cp-metrics
-          image: quay.io/metallb/speaker:v0.14.4
+          image: quay.io/metallb/speaker:v0.14.5
           command: ["/bin/sh", "-c", "cp -f /frr-metrics /etc/frr_metrics/"]
           volumeMounts:
             - name: metrics

diff --git a/config/manifests/metallb-frr-k8s-prometheus.yaml b/config/manifests/metallb-frr-k8s-prometheus.yaml
@@ -2592,7 +2592,7 @@ spec:
           value: memberlist
         - name: METALLB_DEPLOYMENT
           value: controller
-        image: quay.io/metallb/controller:v0.14.4
+        image: quay.io/metallb/controller:v0.14.5
         livenessProbe:
           failureThreshold: 3
           httpGet:
@@ -3067,7 +3067,7 @@ spec:
           value: app=metallb,component=speaker
         - name: METALLB_ML_SECRET_KEY_PATH
           value: /etc/ml_secret_key
-        image: quay.io/metallb/speaker:v0.14.4
+        image: quay.io/metallb/speaker:v0.14.5
         livenessProbe:
           failureThreshold: 3
           httpGet:

diff --git a/config/manifests/metallb-frr-k8s.yaml b/config/manifests/metallb-frr-k8s.yaml
@@ -2497,7 +2497,7 @@ spec:
           value: memberlist
         - name: METALLB_DEPLOYMENT
           value: controller
-        image: quay.io/metallb/controller:v0.14.4
+        image: quay.io/metallb/controller:v0.14.5
         livenessProbe:
           failureThreshold: 3
           httpGet:
@@ -2949,7 +2949,7 @@ spec:
           value: app=metallb,component=speaker
         - name: METALLB_ML_SECRET_KEY_PATH
           value: /etc/ml_secret_key
-        image: quay.io/metallb/speaker:v0.14.4
+        image: quay.io/metallb/speaker:v0.14.5
         livenessProbe:
           failureThreshold: 3
           httpGet:

diff --git a/config/manifests/metallb-frr-prometheus.yaml b/config/manifests/metallb-frr-prometheus.yaml
@@ -1870,7 +1870,7 @@ spec:
           value: memberlist
         - name: METALLB_DEPLOYMENT
           value: controller
-        image: quay.io/metallb/controller:v0.14.4
+        image: quay.io/metallb/controller:v0.14.5
         livenessProbe:
           failureThreshold: 3
           httpGet:
@@ -2092,7 +2092,7 @@ spec:
           value: app=metallb,component=speaker
         - name: METALLB_ML_SECRET_KEY_PATH
           value: /etc/ml_secret_key
-        image: quay.io/metallb/speaker:v0.14.4
+        image: quay.io/metallb/speaker:v0.14.5
         livenessProbe:
           failureThreshold: 3
           httpGet:
@@ -2157,7 +2157,7 @@ spec:
         - /bin/sh
         - -c
         - cp -f /frr-reloader.sh /etc/frr_reloader/
-        image: quay.io/metallb/speaker:v0.14.4
+        image: quay.io/metallb/speaker:v0.14.5
         name: cp-reloader
         volumeMounts:
         - mountPath: /etc/frr_reloader
@@ -2166,7 +2166,7 @@ spec:
         - /bin/sh
         - -c
         - cp -f /frr-metrics /etc/frr_metrics/
-        image: quay.io/metallb/speaker:v0.14.4
+        image: quay.io/metallb/speaker:v0.14.5
         name: cp-metrics
         volumeMounts:
         - mountPath: /etc/frr_metrics

diff --git a/config/manifests/metallb-frr.yaml b/config/manifests/metallb-frr.yaml
@@ -1749,7 +1749,7 @@ spec:
           value: memberlist
         - name: METALLB_DEPLOYMENT
           value: controller
-        image: quay.io/metallb/controller:v0.14.4
+        image: quay.io/metallb/controller:v0.14.5
         livenessProbe:
           failureThreshold: 3
           httpGet:
@@ -1915,7 +1915,7 @@ spec:
           value: app=metallb,component=speaker
         - name: METALLB_ML_SECRET_KEY_PATH
           value: /etc/ml_secret_key
-        image: quay.io/metallb/speaker:v0.14.4
+        image: quay.io/metallb/speaker:v0.14.5
         livenessProbe:
           failureThreshold: 3
           httpGet:
@@ -1980,7 +1980,7 @@ spec:
         - /bin/sh
         - -c
         - cp -f /frr-reloader.sh /etc/frr_reloader/
-        image: quay.io/metallb/speaker:v0.14.4
+        image: quay.io/metallb/speaker:v0.14.5
         name: cp-reloader
         volumeMounts:
         - mountPath: /etc/frr_reloader
@@ -1989,7 +1989,7 @@ spec:
         - /bin/sh
         - -c
         - cp -f /frr-metrics /etc/frr_metrics/
-        image: quay.io/metallb/speaker:v0.14.4
+        image: quay.io/metallb/speaker:v0.14.5
         name: cp-metrics
         volumeMounts:
         - mountPath: /etc/frr_metrics

diff --git a/config/manifests/metallb-native-prometheus.yaml b/config/manifests/metallb-native-prometheus.yaml
@@ -1767,7 +1767,7 @@ spec:
           value: memberlist
         - name: METALLB_DEPLOYMENT
           value: controller
-        image: quay.io/metallb/controller:v0.14.4
+        image: quay.io/metallb/controller:v0.14.5
         livenessProbe:
           failureThreshold: 3
           httpGet:
@@ -1888,7 +1888,7 @@ spec:
           value: app=metallb,component=speaker
         - name: METALLB_ML_SECRET_KEY_PATH
           value: /etc/ml_secret_key
-        image: quay.io/metallb/speaker:v0.14.4
+        image: quay.io/metallb/speaker:v0.14.5
         livenessProbe:
           failureThreshold: 3
           httpGet:

diff --git a/config/manifests/metallb-native.yaml b/config/manifests/metallb-native.yaml
@@ -1649,7 +1649,7 @@ spec:
           value: memberlist
         - name: METALLB_DEPLOYMENT
           value: controller
-        image: quay.io/metallb/controller:v0.14.4
+        image: quay.io/metallb/controller:v0.14.5
         livenessProbe:
           failureThreshold: 3
           httpGet:
@@ -1742,7 +1742,7 @@ spec:
           value: app=metallb,component=speaker
         - name: METALLB_ML_SECRET_KEY_PATH
           value: /etc/ml_secret_key
-        image: quay.io/metallb/speaker:v0.14.4
+        image: quay.io/metallb/speaker:v0.14.5
         livenessProbe:
           failureThreshold: 3
           httpGet:

diff --git a/internal/version/version.go b/internal/version/version.go
@@ -8,7 +8,7 @@ import (
 )
 
 var (
-	version   = "0.14.4"
+	version   = "0.14.5"
 	gitCommit string // Provided by ldflags during build
 	gitBranch string // Provided by ldflags during build
 )

diff --git a/website/content/_header.md b/website/content/_header.md
@@ -1,5 +1,5 @@
 ---
 ---
 <img align="left" src="/images/logo/metallb-white.png" width="25%"></img>
-MetalLB v0.14.4
+MetalLB v0.14.5
 <p style="clear: both"></p>
diff --git a/website/content/community/_index.md b/website/content/community/_index.md
@@ -59,7 +59,7 @@ information on using pull requests.
 By contributing to this project you agree to the Developer Certificate of
 Origin (DCO). This document was created by the Linux Kernel community and is a
 simple statement that you, as a contributor, have the legal right to make the
-contribution. See the [DCO](https://github.com/metallb/metallb/blob/v0.14.4/DCO)
+contribution. See the [DCO](https://github.com/metallb/metallb/blob/v0.14.5/DCO)
 file for details.
 
 ## Code organization

diff --git a/website/content/community/maintainers.md b/website/content/community/maintainers.md
@@ -10,7 +10,7 @@ MetalLB development and maintenance is led by a team of current maintainers.
 MetalLB maintainers are participants in the project with the ability to approve
 changes to the MetalLB code base. The current list of maintainers can be found
 in the [MetalLB CODEOWNERS
-file](https://github.com/metallb/metallb/blob/v0.14.4/CODEOWNERS).
+file](https://github.com/metallb/metallb/blob/v0.14.5/CODEOWNERS).
 
 ## Maintainer Expectations
 

diff --git a/website/content/configuration/_index.md b/website/content/configuration/_index.md
@@ -8,7 +8,7 @@ creating and deploying various resources into **the same namespace**
 (metallb-system) MetalLB is deployed into.
 
 There are various examples of the configuration CRs in
-[`configsamples`](https://github.com/metallb/metallb/tree/v0.14.4/configsamples).
+[`configsamples`](https://github.com/metallb/metallb/tree/v0.14.5/configsamples).
 
 Also, the API is [fully documented here](../apis/).
 

diff --git a/website/content/installation/_index.md b/website/content/installation/_index.md
@@ -59,20 +59,20 @@ kubectl apply -f - -n kube-system
 To install MetalLB, apply the manifest:
 
 ```bash
-kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.14.4/config/manifests/metallb-native.yaml
+kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.14.5/config/manifests/metallb-native.yaml
 ```
 
 {{% notice note %}}
 If you want to deploy MetalLB using the [FRR mode](https://metallb.universe.tf/configuration/#enabling-bfd-support-for-bgp-sessions), apply the manifests:
 
 ```bash
-kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.14.4/config/manifests/metallb-frr.yaml
+kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.14.5/config/manifests/metallb-frr.yaml
 ```
 
 If you want to deploy MetalLB using the [experimental FRR-K8s mode]({{% relref "concepts/bgp.md" %}}#frr-k8s-mode):
 
 ```bash
-kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.14.4/config/manifests/metallb-frr-k8s.yaml
+kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.14.5/config/manifests/metallb-frr-k8s.yaml
 ```
 
 Please do note that these manifests deploy MetalLB from the main development branch. We highly encourage cloud operators to deploy a stable released version of MetalLB on production environments!
@@ -101,7 +101,7 @@ need to be changed.
 
 {{% notice note %}}
 
-You may notice the "prometheus" variants of the manifests (for example `https://raw.githubusercontent.com/metallb/metallb/v0.14.4/config/manifests/metallb-native-prometheus.yaml`).
+You may notice the "prometheus" variants of the manifests (for example `https://raw.githubusercontent.com/metallb/metallb/v0.14.5/config/manifests/metallb-native-prometheus.yaml`).
 Those manifests rely on a very specific way of deploying Prometheus via the [kube prometheus](https://github.com/prometheus-operator/kube-prometheus) repository, and
 are mainly used by our CI, but they might not be compatible to your Prometheus deployment.
 
@@ -120,7 +120,7 @@ In the following example, we are deploying MetalLB with the native bgp implement
 namespace: metallb-system
 
 resources:
-  - github.com/metallb/metallb/config/native?ref=v0.14.4
+  - github.com/metallb/metallb/config/native?ref=v0.14.5
 ```
 
 In order to deploy the [FRR mode](https://metallb.universe.tf/configuration/#enabling-bfd-support-for-bgp-sessions):
@@ -130,7 +130,7 @@ In order to deploy the [FRR mode](https://metallb.universe.tf/configuration/#ena
 namespace: metallb-system
 
 resources:
-  - github.com/metallb/metallb/config/frr?ref=v0.14.4
+  - github.com/metallb/metallb/config/frr?ref=v0.14.5
 ```
 
 In order to deploy the [experimental FRR-K8s mode]({{% relref "concepts/bgp.md" %}}#frr-k8s-mode):

diff --git a/website/content/troubleshooting/_index.md b/website/content/troubleshooting/_index.md
@@ -280,7 +280,7 @@ be set manually.
 
 ### How to fetch the logs and the CRs
 
-A convenience script that fetches all the required information [can be found here](https://raw.githubusercontent.com/metallb/metallb/v0.14.4/troubleshooting/collect.sh).
+A convenience script that fetches all the required information [can be found here](https://raw.githubusercontent.com/metallb/metallb/v0.14.5/troubleshooting/collect.sh).
 
 Additionally, the status of the service and of the endpoints must be provided: