Skip to content

Experimental build targetting fluent-bit branches/tags #931

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: experimental
Choose a base branch
from

Conversation

ShelbyZ
Copy link
Contributor

@ShelbyZ ShelbyZ commented May 21, 2025

Summary

Adds support for building fluent-bit versions into aws-for-fluent-bit container images beyond v1.9.10. Builds against newer versions use an environment variable FLB_TAG to target fluent-bit branches or tags on the core repository - https://github.com/fluent/fluent-bit

No cherry-picks from https://github.com/amazon-contributing/upstream-to-fluent-bit are applied during build.

A new /experimental/README.md has been added to detail the steps required to locally build and publish images to an ECR repository for use.

Issue #, if available:

Testing

Some initial internal testing against integration tests has been conducted for v3.2.10 and v4.0.0 but nothing concrete/verified, so use at your own discretion.

make debug succeeded: yes
Integ tests succeeded: yes
New tests cover the changes: no

Licensing

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ShelbyZ ShelbyZ requested a review from a team as a code owner May 21, 2025 23:35
@swapneils
Copy link
Contributor

Can we name this branch something specific to the features it contains, while maintaining the experimental keyword? E.g. experimental-v3 or experimental-use-upstream-fluent-bit?

I don't want to occupy the general "experimental" name for project-specific code, and preferably we should also make it clear that this branch will be abandoned or deleted once we can properly test and publish images targeting upstream.

Can the warning in the README also note that this branch will lose support once we are publishing more stable versions directly to ECR?

Copy link
Contributor

@swapneils swapneils left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tagging the above comment (#931 (comment)) as requested changes for GitHub to notice it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants