Add revisionHistoryLimit support to aws-for-fluent-bit values

aws · Jun 18, 2024 · eef7317 · eef7317
1 parent 728b05a
commit eef7317
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 1 deletion.
diff --git a/stable/aws-for-fluent-bit/Chart.yaml b/stable/aws-for-fluent-bit/Chart.yaml
@@ -1,7 +1,7 @@
 apiVersion: v1
 name: aws-for-fluent-bit
 description: A Helm chart to deploy aws-for-fluent-bit project
-version: 0.1.33
+version: 0.1.34
 appVersion: 2.32.2.20240425
 home: https://github.com/aws/eks-charts
 icon: https://raw.githubusercontent.com/aws/eks-charts/master/docs/logo/aws.png

diff --git a/stable/aws-for-fluent-bit/README.md b/stable/aws-for-fluent-bit/README.md
@@ -208,6 +208,7 @@ helm delete aws-for-fluent-bit --namespace kube-system
 | `env`| Optional List of pod environment variables for the pods |`[]`|
 | `livenessProbe`| Optional yaml to define liveness probe - In order for liveness probe to work correctly defaults have been set in `service.extraService`, [details](https://docs.fluentbit.io/manual/administration/monitoring#health-check-for-fluent-bit) |httpGet:<br> &nbsp;&nbsp; path: /api/v1/health <br> &nbsp;&nbsp; port: 2020 <br> &nbsp;&nbsp; scheme: HTTP <br> failureThreshold: 2 <br> initialDelaySeconds: 30 <br> timeoutSeconds: 10 |
 | `readinessProbe`| Optional yaml to define readiness probe |`{}`|
+| `revisionHistoryLimit`| Number of revisions to keep | 10 |
 | `serviceMonitor.enabled`| Whether serviceMonitor should be enabled or not, [details](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/getting-started.md) |`false`| ✔ |`[]`|
 | `serviceMonitor.service.type`| Type of service to be created - options are ClusterIP, NodePort, LoadBalancer, ExternalName - [details](https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types) |`ClusterIP`|
 | `serviceMonitor.service.port`| Incoming TCP port of the kubernetes service - Traffic is routed from this port to the targetPort to gain access to the application -  By default and for convenience, the targetPort is set to the same value as the port field. [details](https://kubernetes.io/docs/concepts/services-networking/service/#defining-a-service) | 2020 |

diff --git a/stable/aws-for-fluent-bit/templates/daemonset.yaml b/stable/aws-for-fluent-bit/templates/daemonset.yaml
@@ -8,6 +8,7 @@ metadata:
 spec:
   updateStrategy:
 {{ toYaml .Values.updateStrategy | indent 4 }}
+  revisionHistoryLimit: {{ .Values.revisionHistoryLimit }}
   selector:
     matchLabels:
       {{- include "aws-for-fluent-bit.selectorLabels" . | nindent 6 }}

diff --git a/stable/aws-for-fluent-bit/values.yaml b/stable/aws-for-fluent-bit/values.yaml
@@ -283,6 +283,8 @@ resources:
     cpu: 50m
     memory: 50Mi
 
+revisionHistoryLimit: 10
+
 ## Assign a PriorityClassName to pods if set
 # priorityClassName: system-node-critical