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 cos-auditd-logging.yaml to replace fluent-bit image #53

Merged
merged 2 commits into from
Dec 16, 2024

Conversation

baizhenyu
Copy link
Contributor

@baizhenyu baizhenyu commented Dec 3, 2024

  • Replace internal fluent-bit image with latest OSS one
  • Remove deprecated fluent-bit config settings in latest

Replace internal fluent-bit image with latest OSS one
@baizhenyu
Copy link
Contributor Author

/assign @SergeyKanzhelev

Copy link
Contributor

@giuliano-sider giuliano-sider left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -71,7 +71,7 @@ spec:
value: "$CLUSTER_NAME"
- name: CLUSTER_LOCATION
value: "$CLUSTER_LOCATION"
image: gke.gcr.io/fluent-bit@sha256:b148f7f960f101b6d52efd909fe43fef73cb40cee3571da61034974965605b66 # v1.8.12-gke.31
image: fluent/fluent-bit:latest
Copy link
Collaborator

Choose a reason for hiding this comment

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

is it a good practice to use latest and suggest to use one from dockerhub?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I discussed internally with my teammates and we believe there is no harm for the cx to use OSS version of image in this particular case since we only provide an example to setup audit logging in COS.

Regarding using latest, the purpose is to reduce potential cx tickets due to mismatched version of libsystemd used to compile fluent-bit and the one used in COS. We agree that it will break at some point (e.g fluent-bit change config format etc) but it is fine to update this file again later.

Copy link

Choose a reason for hiding this comment

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

We discussed internally and we support this solution in a "best effort" way and would like to highlight that this is a solution depending on OSS tool - hence suggesting use the latest dockerhub image.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Please add a comment above this line suggesting to change it. Something like:

Suggested change
image: fluent/fluent-bit:latest
# this image is used for demo purposes. The best practice is to use the image from controlled registry and reference it by SHA.
image: fluent/fluent-bit:latest

Copy link
Collaborator

Choose a reason for hiding this comment

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

Extra credit for mentioning this in the docs: https://cloud.google.com/kubernetes-engine/docs/how-to/linux-auditd-logging as well

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The notes have been added and we will update the public doc later.

@erain
Copy link

erain commented Dec 6, 2024

LGTM.

Replace internal fluent-bit image with latest OSS one
@SergeyKanzhelev SergeyKanzhelev merged commit 9dd058e into GoogleCloudPlatform:master Dec 16, 2024
1 check passed
@baizhenyu baizhenyu deleted the patch-1 branch December 16, 2024 19:55
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.

4 participants