Skip to content

Expose blind_write in fluent-plugin-gcs #1950

Open
@YorithTheDreamer

Description

@YorithTheDreamer

Is your feature request related to a problem? Please describe.
We are using nearline and archive clsss storage for some of the logs we are saving.

Typical operational costs are driven up dramatically by the fact the storage.object.get is being run constantly from this block in the plug in:

https://github.com/kube-logging/fluent-plugin-gcs/blob/ad6a7cb0f166e2c1648954a928e1e9b8cdcbf93d/lib/fluent/plugin/out_gcs.rb#L163-L169

Describe the solution you'd like
Expose blind_write in the gcs output struct so it can be part of the fluentd output

Describe alternatives you've considered
We could use a different storage class, but in the long term this would be more expensive.

Activity

added this to the 5.x milestone on Mar 4, 2025
stale

stale commented on May 5, 2025

@stale

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Expose blind_write in fluent-plugin-gcs · Issue #1950 · kube-logging/logging-operator