-
Notifications
You must be signed in to change notification settings - Fork 512
installation: switch to YAML config files by default #1551
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Patrick Stephens <pat@chronosphere.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
made a few suggestions for clarity—although let me know if I misunderstood anything and made suggestions that don't make sense 😅
@@ -9,6 +9,15 @@ Note: release notes will be prepared in advance of a Git tag for a release so an | |||
The tag drives the overall binary release process so release binaries (containers/packages) will appear after a tag and its associated release note. | |||
This allows users to expect the new release binary to appear and allow/deny/update it as appropriate in their infrastructure. | |||
|
|||
## Fluent Bit v4.0+ | |||
|
|||
The default configuration file has been switched to use YAML format and a different name (`.yaml` file suffix instead of `.conf`). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The default configuration file has been switched to use YAML format and a different name (`.yaml` file suffix instead of `.conf`). | |
By default, configuration files use YAML syntax and the `.yaml` file extension. |
|
||
The default configuration file has been switched to use YAML format and a different name (`.yaml` file suffix instead of `.conf`). | ||
|
||
This may require updating any custom deployments to either provide a YAML configuration or switch back to using legacy configuration in the arguments to the Fluent Bit binary. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This may require updating any custom deployments to either provide a YAML configuration or switch back to using legacy configuration in the arguments to the Fluent Bit binary. | |
You may need to update your custom deployments to either use YAML configuration files | |
or switch back to using legacy configuration in the arguments to the Fluent Bit binary. |
For Linux the Systemd unit will need overriding to specify `-c <legacy config file>`. | ||
Similarly for containers, Windows and macOS the default launch command is changed to point at the YAML config file by default. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For Linux the Systemd unit will need overriding to specify `-c <legacy config file>`. | |
Similarly for containers, Windows and macOS the default launch command is changed to point at the YAML config file by default. | |
In Linux environments, you must override the systemd unit to specify `-c <legacy config file>`. | |
Similarly, in Windows and macOS container environments, the default launch command uses YAML configuration files | |
by default. |
See fluent/fluent-bit#9837, update to use YAML config by default.
I have not tackled providing YAML config for all installation options in the docs, this is mostly to cover the upgrade impact. Ideally @fluent/chronosphere-tech-writers we can also update all the legacy config in the docs to also have a YAML config example by default.