-
Notifications
You must be signed in to change notification settings - Fork 252
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
help request: option to ignore not valid output cr instance #943
Labels
good first issue
Good for newcomers
Comments
rmechi
changed the title
option to ignore not valid output cr instance
help request: option to ignore not valid output cr instance
Oct 2, 2023
This one requires you to provide the contents of the secret configuration file. |
Thanks for the Replay. copy pasting decoded app.conf:
fluent.conf:
log.conf:
system.conf:
|
if any one of below targets does not work, fluentd start refusing the connections.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue
namespace-a
and everything else underspec.outputs
exist ( ex. roles ) and valid. no issues when fluentd reload . everything look good.create output for
namespace-c
,namespace-d
,namespace-e
and everything else underspec.outputs
exist ( ex. roles ) and valid. no issues when fluentd reload . everything look good.Now, create output for
namespace-f
with non existing role.Now, role mentioned under
awsStsRoleArn
not exist. when fluentd reloads-> fluent bit throuw
TCP connection failed: fluentd.fluent.svc.cluster.local:24224 (Connection refused)
-> fluentd throw something like
_class=Aws::STS::Errors::AccessDenied error="User: arn:aws:sts::757575757:assumed-role/hub-role/NjVmNTJkNjUtYTFkMC00MzY1LWJhNjctN2M1MWZmMmY1Mjhl is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::74658383::role/spoke-role"
after creating
Output
fornamespace-f
with non existing role. fluentd started refusing connections impacting whole cluster i.e. all other namespaces those have valid configurations throughOutput
object.any way to ignore or not to process the
output
instances those have non woking configuration ? ex. role not exist or target not listening etc. because one non workingoutput
object impact thousands of other namespace logging those have validOutput
configuration as i see one not workingOutput
leadingfluentd
pod to refuse the connection.How did you install fluent operator?
using helm chart. operator version
1.7.0
Additional context
No response
The text was updated successfully, but these errors were encountered: