upgrade fluent-bit

[zubenkoivan]

Closes #837

Fluent Bit in recent versions introduced new AWS S3 plugin which is able to put logs directly to object storage. Currently we use Fluentd to forward logs to object storage.

PR contains following changes:

• Fluent Bit upgrade
• Switched Fluent Bit to use s3 plugin for output
• Removed Fluentd
• For GCP and Azure object storages deploy Minio gateway service to conform them to S3 API
• Make integration tests more stable

[codecov]

Codecov Report

Merging #842 (aaaaa8e) into master (061c989) will decrease coverage by 0.65%.
Report is 2 commits behind head on master.
The diff coverage is 69.23%.

@@            Coverage Diff             @@
##           master     #842      +/-   ##
==========================================
- Coverage   86.41%   85.76%   -0.65%     
==========================================
  Files          12       12              
  Lines        2090     2100      +10     
  Branches      289      290       +1     
==========================================
- Hits         1806     1801       -5     
- Misses        173      187      +14     
- Partials      111      112       +1     

Flag	Coverage Δ
integration	79.80% <69.23%> (-0.77%)	⬇️
unit	47.23% <23.07%> (-0.14%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
platform_monitoring/logs.py	84.94% <100.00%> (-2.59%)	⬇️
platform_monitoring/api.py	81.33% <66.66%> (-0.45%)	⬇️

[dalazx]

looks great. how will this solution handle existing old logs in all our clusters?

[zubenkoivan]

Changes are backward compatible. S3 plugin writes log files with the same S3 key prefix /$TAG/%Y%m%d%H%M as Fluentd did before, so S3LogReader will be able to parse old and new logs the same way and sort them correctly.

[dalazx]

excellent. thank you!