installation: switch to YAML config files by default #1551
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Patrick Stephens <[email protected]>
7 tasks
alexakreizinger
approved these changes
Jan 17, 2025
| @@ -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.
Suggested change
| 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.
Suggested change
| 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. |
Comment on lines
+18
to
+19
| 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.
Suggested change
| 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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.