Skip to content
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

Update fluent-bit to latest #90

Closed
wants to merge 1 commit into from
Closed

Conversation

bkh4mmm
Copy link

@bkh4mmm bkh4mmm commented Apr 4, 2022

Latest is current 2.23.0. Version 2.10.0 is outdated.

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Latest is current 2.23.0. Version 2.10.0 is outdated.
@@ -464,7 +464,7 @@ spec:
spec:
containers:
- name: fluent-bit
image: amazon/aws-for-fluent-bit:2.10.0
image: amazon/aws-for-fluent-bit:latest
Copy link
Contributor

Choose a reason for hiding this comment

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

Personally, I think we need a good way to continuously test/verify the daemonsets before I'd be comfortable switching to use the latest tagged image. AFAIK tests for container insights only really happen when ramping up for a release of the agent, so I'd like to have proper integration testing set up prior to approving and merging this in. Whether it happens on this repo or the CloudWatch agent repo, I'm indifferent, but I did cut an issue in the CloudWatch agent repo to at least document this somewhere.

@SaxyPandaBear
Copy link
Contributor

I think #95 is the better approach to pin to a release that is declared as stable rather than the latest.

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.

2 participants