add a new blog: Fluent Bit Operator becomes an official sub-project of the Fluent Community #24
Conversation
FeynmanZhou
force-pushed
the
master
branch
2 times, most recently
from
817a199
to
db9f997
Compare
FeynmanZhou
force-pushed
the
master
branch
3 times, most recently
from
c26b661
to
acb7e84
Compare
…f the Fluent Community Signed-off-by: FeynmanZhou <pengfeizhou@yunify.com>
| author: Feynman Zhou(https://github.com/FeynmanZhou) | ||
| --- | ||
|
|
||
| # Fluent Bit Operator becomes an official sub-project of the Fluent Community! |
There was a problem hiding this comment.
i think we also need to explain the motivations of the following:
- Fluent Bit / Fluentd are deployed a lot within Kubernetes
- The importance of Operators within Kubernetes, and how they help users
- Why we have added this project within the Fluent organization
There was a problem hiding this comment.
For 1 and 2, I can add more detailed explanations. For the third one, could you please also give one brief reason that why Fluent organization chose to accept Fluent Operator as a sub-project?
| # Fluent Bit Operator becomes an official sub-project of the Fluent Community! | ||
|
|
||
| [Fluent Bit Operator](https://github.com/fluent/fluentbit-operator) is the only existing operator which facilitates the deployment of [Fluent Bit](https://fluentbit.io/) and provides great flexibility in building a logging layer based on Fluent Bit and Kubernetes. With a dedicated observability team at [KubeSphere](https://kubesphere.io) created this project, multiple maintainers from [DigitalOcean](https://www.digitalocean.com/) and other organizations have been maintaining it for almost three years and delivered 12 major releases, today we are glad to announce that Fluent Operator has become an official sub-project of the Fluent Community! | ||
|
|
There was a problem hiding this comment.
I would move the getting started piece up here as the main Call to Action
|
|
||
| ## Why Fluent Bit Operator | ||
|
|
||
| As the dynamic configuration reloading without restart is not supported in Fluent Bit and it [has been asked in the community](https://github.com/fluent/fluent-bit/issues/365) for several years, the KubeSphere team initiated the Fluent Bit Operator to enable Fluent Bit to pick up and use the latest config whenever the Fluent Bit config changes without restarting the Fluent Bit Pod. |
There was a problem hiding this comment.
While the config reloading is important I really like the focus you have on the three bullets below. "The Fluent Bit Operator provides three main benefits..." from there I feel it would be good to eloborate on each one and mention some of the benefits over a traditional helm-chart / daemonset deployment
There was a problem hiding this comment.
Good suggesion! I will elaborate on them.
| {:class="img-responsive"} | ||
|
|
||
| ## Evolving to the Fluent Operator | ||
|
|
There was a problem hiding this comment.
I would also mention the metrics piece that was added in Fluent Bit and how that will be coming in the operator as well
|
|
||
| You are welcome to create issues and pull requests. We are actively resolving community issues, host community meetings, and providing answers on a dedicated [Slack channel](https://fluent-all.slack.com/archives/C02642TE9HR). | ||
|
|
||
| If you still haven’t used Fluent Bit Operator, you’re welcome to try it now by following the [quick start](https://github.com/fluent/fluentbit-operator#install). Let's discover more simplicity of running Fluent Bit Operator on Kubernetes. |
There was a problem hiding this comment.
From comment above, I would move this part to right after the intro for a faster CTA and hopefully more conversion
There was a problem hiding this comment.
Make sense, I will move it to the first paragraph.
Ref: #23