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

Cannot add storage.path attribute to fluent-bit.conf [SERVICE] section #559

Open
deftones65 opened this issue Jul 15, 2021 · 2 comments · May be fixed by #1168
Open

Cannot add storage.path attribute to fluent-bit.conf [SERVICE] section #559

deftones65 opened this issue Jul 15, 2021 · 2 comments · May be fixed by #1168
Labels
bug Something isn't working

Comments

@deftones65
Copy link

deftones65 commented Jul 15, 2021

Describe the bug

I suspect this isn't a bug, but not sure how to achieve this. I am installing this chart, and configuring the exact setup from AWS tutorial on setting up FluentBit:
https://raw.githubusercontent.com/aws-samples/amazon-cloudwatch-container-insights/latest/k8s-deployment-manifest-templates/deployment-mode/daemonset/container-insights-monitoring/fluent-bit/fluent-bit.yaml

To be more precise, I am creating values.yaml mimicking the above manual way of doing it.

The above manifest has storage attributes configured:

   ```
   [SERVICE]
    Flush                     5
    Log_Level                 info
    Daemon                    off
    Parsers_File              parsers.conf
    HTTP_Server               ${HTTP_SERVER}
    HTTP_Listen               0.0.0.0
    HTTP_Port                 ${HTTP_PORT}
    storage.path              /var/fluent-bit/state/flb-storage/
    storage.sync              normal
    storage.checksum          off
    storage.backlog.mem_limit 5M
    ```

But chart configuration doesn't allow to add anything in that section apart from parser files. Is there a way to accomplish this?

  • Chart name: AWS-for-fluent-bit
  • Chart version: 0.1.11
  • Kubernetes version: 1.19
  • Using EKS (yes/no), if so version? YES, 1.19
@deftones65 deftones65 added the bug Something isn't working label Jul 15, 2021
@endersonmaia
Copy link

related to #510

@nikki-quant
Copy link

Hi, I'd also like this - it doesn't seem like fluent bit is able to default that value and you can't use storage.type = filesystem for individual inputs without it, which is recommended for anyone having issues with memory.

Currently there are two Helm-parameterised sections within the [SERVICE] block:

| `service.parsersFiles` | List of available parser files | `/fluent-bit/parsers/parsers.conf` |
| `service.extraParsers` | Adding more parsers with this value | `""` |

Maintainers, would you welcome a PR to add a service.storagePath option to the chart, and if so what would you like as a default value?

vsimon pushed a commit to vsimon/eks-charts that referenced this issue Dec 9, 2021
vsimon pushed a commit to vsimon/eks-charts that referenced this issue Dec 9, 2021
Kaawin1 pushed a commit to Kaawin1/eks-charts that referenced this issue Jan 11, 2022
vsimon pushed a commit to vsimon/eks-charts that referenced this issue Jan 13, 2022
vsimon pushed a commit to vsimon/eks-charts that referenced this issue Feb 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
3 participants