Bump version to 0.0.5

Makefile

@@ -3,7 +3,7 @@
 # To re-generate a bundle for another specific version without changing the standard setup, you can:
 # - use the VERSION as arg of the bundle target (e.g make bundle VERSION=0.0.2)
 # - use environment variables to overwrite this value (e.g export VERSION=0.0.2)
-VERSION ?= 0.0.4
+VERSION ?= 0.0.5
 
 # CHANNELS define the bundle channels used in the bundle.
 # Add a new line here if you would like to change its default config. (E.g CHANNELS = "candidate,fast,stable")

bundle/manifests/istio-fortsa.clusterserviceversion.yaml

@@ -4,10 +4,10 @@ metadata:
   annotations:
     alm-examples: '[]'
     capabilities: Basic Install
-    createdAt: "2024-10-27T02:13:27Z"
+    createdAt: "2024-10-27T14:59:27Z"
     operators.operatorframework.io/builder: operator-sdk-v1.36.1
     operators.operatorframework.io/project_layout: go.kubebuilder.io/v4
-  name: istio-fortsa.v0.0.4
+  name: istio-fortsa.v0.0.5
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -136,7 +136,7 @@ spec:
                 - --leader-elect
                 command:
                 - /manager
-                image: ghcr.io/hercynium/istio-fortsa:0.0.4
+                image: ghcr.io/hercynium/istio-fortsa:0.0.5
                 livenessProbe:
                   httpGet:
                     path: /healthz

chart/istio-fortsa/values.yaml

@@ -39,7 +39,7 @@ controllerManager:
         - ALL
     image:
       repository: ghcr.io/hercynium/istio-fortsa
-      tag: 0.0.4
+      tag: 0.0.5
     resources:
       limits:
         cpu: 500m

config/manager/kustomization.yaml

@@ -5,4 +5,4 @@ kind: Kustomization
 images:
 - name: controller
   newName: ghcr.io/hercynium/istio-fortsa
-  newTag: 0.0.4
+  newTag: 0.0.5