Bug 1348583
Summary: | [RFE] Method to Modify Fluentd Configuration Simplified | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Steven Walter <stwalter> |
Component: | RFE | Assignee: | ewolinet |
Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.2.0 | CC: | aos-bugs, jokerman, lmeyer, mmccomas, rmeggins, tdawson |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-27 09:38:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Steven Walter
2016-06-21 13:46:17 UTC
@eric, how do these changes relate to our move to configmaps? @Jeff, Currently we have not tried to implement this with configmaps in Fluentd. During previous discussions we weren't sure if configmaps would be applicable for being able to accomplish this give how the Fluend config is structured. I think under OSE you could do this in the short term by mounting a secret or configmap at /etc/fluent with fluent.conf in it; as long as the keys secret mounted on top of that, it ought to carry on and that would make it pretty easy to reconfigure. It's not clear how well this will work in the future with the refactored fluent config that's in origin. We're discussing how best to proceed. Clearly there are going to be customers wanting this type of configuration. Is this feature needed in 3.3? This will be available in 3.3 via configmaps. Documentation is currently being worked on here: https://github.com/openshift/openshift-docs/pull/2538 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1933 |