[kots]: ensure log-collector directory on node at startup #13233
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.
Description
This ensures that the
/gitpod/log-collector
directory exists on every node at FluentBit startup. Previously, this directory was only created when a log was added which meant that thelog-collector
section in a support bundle was full ofconfigmap-errors
saying that the directory didn't exist.Now, this only adds files into the support bundle if there are files to add, meaning that it's much easier to search for things to look through.
Related Issue(s)
Fixes #13095
How to test
Install via KOTS and generate a support bundle
Release Notes
Documentation
Werft options:
If enabled this will build
install/preview
Valid options are
all
,workspace
,webapp
,ide