samsung-cnct / chart-fluent-bit Goto Github PK

The README refers to fluent-bit.yaml, which no longer exists in this repo.

It would also be great to explain how this chart is a sub-chart of our logging-chart, and provide a link.

Replace "latest" tag with version for our fluent-bit image once our CI can push versioned releases.

From @leahnp on August 1, 2017 23:9

We will use a very similar fluentbit deployment for our 'logging-lite' solution.
Investigate if we can simply add an elasticsearch output plugin to this config and use it for logging-lite or if we need to create a separate repo.

Depending on outcome, make issues to implement the work for a logging-lite fluentbit daemonset with an elasticsearch output plugin.

Copied from original issue: samsung-cnct/kraken-logging-fluent-bit-daemonset#12

Add unit tests for fluent-bit, testing input, output, and filter plugins.

This will involve research on how to set up tests for fluent-bit.

• Follow instructions to edit.gitlab-ci.yml from template The gitlab file is there but we have changed some of the structure since this was a test for the port to gitlab. Please grab the newest version of .gitlab-ci.yml from the template and replace the existing file.
• also replace and edit build/build.sh and build/test.sh according to instructions
• make build.sh and test.sh executable
• create secret variable in gitlab
• add pipeline status badge to README
• Remove the Jenkinsfile in the current repo.
• When PR has merged, make sure that new image is being created on quay. Afterwards, please head back to the umbrella ticket and check off the chart-fluent-bit

From @leahnp on May 17, 2017 0:6

Add memory limit to deployment yaml. Test special case: in long-running clusters with lots of pre-existing logs, deploy Fluent-bit, initial workload is very heavy then it evens out. If it hits the memory limit in this initial processing it will continually be killed and re-created.

Copied from original issue: samsung-cnct/kraken-logging-fluent-bit-daemonset#5