-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
Logging 5.9, Logging 6.0
-
False
-
None
-
False
-
Not Selected
-
0
Proposed title of this feature request
Reload Forwarder secrets when they change.
What is the nature and description of the request?
When the forwarder secret is rotated automatically (for instance when Certificate resource managed is used), the collector pods do not pick up the change and need to be reloaded (through manual deletion of the pods or by defining some third-party automation).
Why does the customer need this? (List the business requirements)
The collector pod could load the new content from the secret, a similar change to what was done inĀ https://issues.redhat.com/browse/LOG-5525
List any affected packages or components.
Vector.