aws / aws/containers-roadmap

[EKS] [request]: EKS Fargate Support for more Fluent Bit output plugins

Open
#1,242 57 comments 302 reactions 0 assignees View on GitHub
EKS Fargate FluentBit Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
I want to use logging to fluentd(forward output) or logstash(http output)

**Which service(s) is this request for?**
EKS on Fargate

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Only CloudWatch, ES, Kinesis are available now as basic EKS Fargate fluent bit functions.

**Are you currently working around this issue?**
I added a fluent-bit container in every pods.

**Additional context**
We hope that the general http & forward output function will be implemented as soon as possible in order for EKS Fargate to become a more practical service.

**Attachments**

Contributor guide

Open the contributing guide

Research direction

The issue names EKS on Fargate and the currently available CloudWatch, ES, and Kinesis Fluent Bit outputs; start by reviewing the roadmap entry and EKS Fargate logging documentation. Compare the requested fluentd forward and logstash HTTP outputs with the supported options, then confirm with maintainers what implementation scope and acceptance criteria would define completion; no source files or tests are identified here.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.