New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LOG-4237: add validation rule that will drop configuration for Splunk output and Fluentd collector #2059
LOG-4237: add validation rule that will drop configuration for Splunk output and Fluentd collector #2059
Conversation
… output and Fluentd collector Signed-off-by: Vitalii Parfonov <vparfono@redhat.com>
@vparfonov: This pull request references LOG-4237 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/hold |
/retest |
/hold cancel |
@vparfonov: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/assign @jcantrill |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cahartma, vparfonov The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
924f716
into
openshift:release-5.7
/cherry-pick master |
@vparfonov: new pull request created: #2064 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Description
This PR addresses the issue where the configuration for
Splunk
output andFluentd
collector, this can lead to unexpected behavior and errors in the system, it because we not supportFluentd
andSplunk
integration (see https://docs.openshift.com/container-platform/4.13/logging/v5_6/logging-5-6-reference.html). To resolve this, we have implemented a new validation rule that will drop the configuration forSplunk
output andFluentd
collector./cc
/assign
/cherry-pick
Links