chore: bump vector version

Signed-off-by: Hornwind <hornwind89@gmail.com>

Author: hornwind

README.md

@@ -38,7 +38,7 @@ Connect us in Telegram - https://t.me/+Y0PzGa1d5DFiYThi
 - Collect journald services logs [doc](https://github.com/kaasops/vector-operator/blob/main/docs/journald-logs.md)
 
 
-## Configuration Examples 
+## Configuration Examples
 Configuration for CR Vector:
 ```yaml
 apiVersion: observability.kaasops.io/v1alpha1
@@ -49,7 +49,7 @@ metadata:
 spec:
   agent:
     service: true
-    image: "timberio/vector:0.24.0-distroless-libc"
+    image: "timberio/vector:0.47.0-distroless-libc"
 ```
 
 Configuration for CR VectorPipeline:
@@ -98,8 +98,8 @@ spec:
 ### How it works
 This project aims to follow the Kubernetes [Operator pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
 
-It uses [Controllers](https://kubernetes.io/docs/concepts/architecture/controller/) 
-which provides a reconcile function responsible for synchronizing resources untile the desired state is reached on the cluster 
+It uses [Controllers](https://kubernetes.io/docs/concepts/architecture/controller/)
+which provides a reconcile function responsible for synchronizing resources untile the desired state is reached on the cluster
 
 ### Test It Out
 1. Install the CRDs into the cluster:

config/samples/observability_v1alpha1_vector.yaml

@@ -5,7 +5,7 @@ metadata:
   namespace: vector
 spec:
   agent:
-    image: "timberio/vector:0.28.1-debian"
+    image: "timberio/vector:0.47.0-debian"
     internalMetrics: false
     api:
       enabled: true
@@ -19,4 +19,3 @@ spec:
       requests:
         cpu: 10m
         memory: 20Mi
-

docs/aggregator.md

@@ -1,6 +1,6 @@
 # Aggregator
 
-The operator allows deploying Vector in the cluster as an aggregator for remote processing, [more details about this](https://vector.dev/docs/setup/going-to-prod/arch/aggregator/). 
+The operator allows deploying Vector in the cluster as an aggregator for remote processing, [more details about this](https://vector.dev/docs/setup/going-to-prod/arch/aggregator/).
 Two types of resources are available for deploying aggregators in the cluster:
 - VectorAggregator
 - ClusterVectorAggregator
@@ -17,7 +17,7 @@ metadata:
   name: vectorAggregator1
   namespace: vector
 spec:
-  image: timberio/vector:0.40.0-debian
+  image: timberio/vector:0.47.0-debian
   api:
     enabled: true
   replicas: 1
@@ -62,7 +62,7 @@ kind: ClusterVectorAggregator
 metadata:
   name: clusterVectorAggregator1
 spec:
-  image: timberio/vector:0.40.0-debian
+  image: timberio/vector:0.47.0-debian
   resourceNamespace: default
   api:
     enabled: true
@@ -105,4 +105,4 @@ spec:
         user: elastic
         password: test-password
         strategy: basic
-```
+```

docs/journald-logs.md

@@ -4,7 +4,7 @@ If you want collect service journald logs from node you can use example.
 
 > Type `journald` in source block work only in ClusterVectorPipeline. In VectorPipeline can use only `kubernetes_logs` type
 
-> If you want collect journald logs, needs to use vector-agent container with journalctl. `timberio/vector:0.26.0-debian` - for example
+> If you want collect journald logs, needs to use vector-agent container with journalctl. `timberio/vector:0.47.0-debian` - for example
 
 
 ```yaml

docs/kubernetes-events.md

@@ -1,7 +1,7 @@
 # [EXPERIMENTAL] Kubernetes events
 
 The operator allows organizing the collection of events from the Kubernetes cluster in which it is deployed.
-To do this, you need to deploy an aggregator and a pipeline. 
+To do this, you need to deploy an aggregator and a pipeline.
 The operator allows collecting events from the entire cluster or from a specific namespace.
 
 ## Namespace event collection
@@ -13,7 +13,7 @@ metadata:
   name: vectorAggregator1
   namespace: vector
 spec:
-  image: timberio/vector:0.40.0-debian
+  image: timberio/vector:0.47.0-debian
   api:
     enabled: true
   replicas: 1
@@ -53,7 +53,7 @@ kind: ClusterVectorAggregator
 metadata:
   name: clusterVectorAggregator1
 spec:
-  image: timberio/vector:0.40.0-debian
+  image: timberio/vector:0.47.0-debian
   resourceNamespace: default
   api:
     enabled: true
@@ -83,4 +83,4 @@ spec:
         codec: "json"
       inputs:
         - source-test
-```
+```

docs/specification.md

@@ -12,7 +12,7 @@
     <tr>
       <td rowspan="25">agent</td>
       <td>image</td>
-      <td>Image for Vector agent. <code>timberio/vector:0.24.0-distroless-libc</code> by default</td>
+      <td>Image for Vector agent. <code>timberio/vector:0.47.0-distroless-libc</code> by default</td>
     </tr>
     <tr>
         <td>dataDir</td>

helm/charts/vector-operator/values.yaml

@@ -78,7 +78,7 @@ vector:
   name: "vector"
   useApiServerCache: false
   # agent:
-  #   image: timberio/vector:0.24.0-distroless-libc
+  #   image: timberio/vector:0.47.0-distroless-libc
   #   env:
   #   - name: "testenv"
   #     value: "testvalues"

internal/vector/aggregator/controller.go

@@ -125,7 +125,7 @@ func (ctrl *Controller) DeleteVectorAggregator(ctx context.Context) error {
 
 func (ctrl *Controller) setDefault() {
 	if ctrl.Spec.Image == "" {
-		ctrl.Spec.Image = "timberio/vector:0.28.1-distroless-libc"
+		ctrl.Spec.Image = "timberio/vector:0.47.0-distroless-libc"
 	}
 
 	if ctrl.Spec.Resources.Requests == nil {

internal/vector/vectoragent/vectoragent_default.go

@@ -28,7 +28,7 @@ func (ctrl *Controller) SetDefault() {
 		ctrl.Vector.Spec.Agent = new(v1alpha1.VectorAgent)
 	}
 	if ctrl.Vector.Spec.Agent.Image == "" {
-		ctrl.Vector.Spec.Agent.Image = "timberio/vector:0.28.1-distroless-libc"
+		ctrl.Vector.Spec.Agent.Image = "timberio/vector:0.47.0-distroless-libc"
 	}
 
 	if ctrl.Vector.Spec.Agent.Resources.Requests == nil {