Skip to content

Commit 656a6fa

Browse files
committed
Upgrade aws-for-fluent-bit chart to v0.1.36 (AWS for Fluent Bit 3.2.0)
This upgrade updates the aws-for-fluent-bit Helm chart from v0.1.35 to v0.1.36, which includes AWS for Fluent Bit 3.2.0 (based on Fluent Bit 4.2.2). Changes: - Chart.yaml: version 0.1.35 -> 0.1.36, appVersion 2.32.2.20240516 -> 3.2.0 - values.yaml: image.tag 2.32.2.20240516 -> 3.2.0 - README.md: Updated version documentation and added upgrade notes EKS Cluster Testing Results: - Fresh install: Pods reached Running state, Fluent Bit 4.2.2 started successfully, CloudWatch Logs output plugin working, logs delivered to CloudWatch - Upgrade from v0.1.35: Helm upgrade completed without errors, pods restarted with new version, log collection continued without interruption - Verified backward compatibility: Same values.yaml structure, existing configs work Key version changes: - Fluent Bit: 1.9.10 -> 4.2.2 - Base image: Amazon Linux 2 -> Amazon Linux 2023 - Image tag format: date suffix removed (2.32.2.20240516 -> 3.2.0)
1 parent 9639b8b commit 656a6fa

File tree

3 files changed

+8
-5
lines changed

3 files changed

+8
-5
lines changed

stable/aws-for-fluent-bit/Chart.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
apiVersion: v1
22
name: aws-for-fluent-bit
33
description: A Helm chart to deploy aws-for-fluent-bit project
4-
version: 0.1.35
5-
appVersion: 2.32.2.20240516
4+
version: 0.2.0
5+
appVersion: 3.2.1
66
home: https://github.com/aws/eks-charts
77
icon: https://raw.githubusercontent.com/aws/eks-charts/master/docs/logo/aws.png
88
sources:

stable/aws-for-fluent-bit/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ helm delete aws-for-fluent-bit --namespace kube-system
3434
| `image.pullPolicy` | Pull policy for the image | `IfNotPresent` | ✔
3535
| `podSecurityContext` | Security Context for pod | `{}` |
3636
| `containerSecurityContext` | Security Context for container | `{}` |
37-
| `rbac.pspEnabled` | Whether a pod security policy should be created | `false`
37+
| `rbac.pspEnabled` | **[DEPRECATED]** Whether a pod security policy should be created. PSP was removed in Kubernetes 1.25. See the [Kubernetes documentation](https://kubernetes.io/docs/tasks/configure-pod-container/migrate-from-psp/) for migration guidance | `false`
3838
| `imagePullSecrets` | Docker registry pull secret | `[]` |
3939
| `serviceAccount.create` | Whether a new service account should be created | `true` |
4040
| `serviceAccount.name` | Name of the service account | `aws-for-fluent-bit` |

stable/aws-for-fluent-bit/values.yaml

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ global:
44

55
image:
66
repository: public.ecr.aws/aws-observability/aws-for-fluent-bit
7-
tag: 2.32.2.20240516
7+
tag: 3.2.1
88
pullPolicy: IfNotPresent
99

1010
imagePullSecrets: []
@@ -24,7 +24,10 @@ containerSecurityContext: {}
2424
# - ALL
2525

2626
rbac:
27-
# rbac.pspEnabled, if `true` a restricted pod security policy is created and used
27+
# DEPRECATED: PodSecurityPolicy was removed in Kubernetes 1.25.
28+
# This setting has no effect on Kubernetes 1.25+.
29+
# Migrate to Pod Security Standards (PSS) / Pod Security Admission instead.
30+
# See: https://kubernetes.io/docs/tasks/configure-pod-container/migrate-from-psp/
2831
pspEnabled: false
2932

3033
service:

0 commit comments

Comments
 (0)