aws / aws/containers-roadmap

[EKS] [request]: EKS 1.30 does not allow forward output plugin out of the box

Open
#2,406 1 comment 0 reactions 0 assignees View on GitHub
EKS Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

Can someone please tell if FluentBit Forward Output plugin is supported in any version of EKS.

I get this error.
Disabled logging for pod due to invalid configmap. forward is not a supported output plugin. Please fix the logging configmap

This is my ConfigMap
kind: ConfigMap
apiVersion: v1
metadata:
name: aws-logging
namespace: aws-observability
data:
flb_log_cw: "false" # Set to true to ship Fluent Bit process logs to CloudWatch.
output.conf: |
[OUTPUT]
Name forward
Match kube.*
Host fluentd-aggregator.default.svc.cluster.local
Port 24224

filters.conf: |
[FILTER]
Name parser
Match *
Key_name log
Parser crio
[FILTER]
Name kubernetes
Match kube.*
Merge_Log On
Keep_Log Off
Buffer_Size 0
Kube_Meta_Cache_TTL 300s

parsers.conf: |
[PARSER]
Name crio
Format Regex
Regex ^(?

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the EKS logging configuration and the supplied aws-logging ConfigMap, especially the Forward output definition. Done would require determining whether EKS supports this plugin and clarifying or implementing the requested support; the issue names no repository files, tests, or implementation entry point.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.