-
Notifications
You must be signed in to change notification settings - Fork 332
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
Secret not found error not reported in Output status #1140
Labels
Milestone
Comments
pepov
added
enhancement
New feature or request
and removed
wontfix
This will not be worked on
bug
Something isn't working
labels
Apr 12, 2023
Idea: the validation reconciler runs after the configuration is generated so in theory we can already depend on the loggingResources variable which contains all the outputs to also register and associate the error with the given outputs and let the validation reconciler report it in the status. |
mzeevi
added a commit
to mzeevi/container-app-operator
that referenced
this issue
Apr 22, 2024
When a user wants logging, now automatcially SyslogNGOutput and SyslogNGFlow objects are created. In addition, support for Splunk has been removed and only Elasticsearch Outputs are supported. A test case has been modified due to a known issue whiich should be fixed in the next release of loggig-operator (kube-logging/logging-operator#1140) Signed-off-by: mzeevi <[email protected]>
mzeevi
added a commit
to mzeevi/container-app-operator
that referenced
this issue
Apr 22, 2024
When a user wants logging, now automatcially SyslogNGOutput and SyslogNGFlow objects are created. In addition, support for Splunk has been removed and only Elasticsearch Outputs are supported. A test case has been modified due to a known issue whiich should be fixed in the next release of loggig-operator (kube-logging/logging-operator#1140) Signed-off-by: mzeevi <[email protected]>
mzeevi
added a commit
to mzeevi/container-app-operator
that referenced
this issue
Apr 22, 2024
When a user wants logging, now automatcially SyslogNGOutput and SyslogNGFlow objects are created. In addition, support for Splunk has been removed and only Elasticsearch Outputs are supported. A test case has been modified due to a known issue whiich should be fixed in the next release of loggig-operator (kube-logging/logging-operator#1140) Signed-off-by: mzeevi <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug:
If an Output references a wrong or inexistent secret, the error is not reported into the Output's status.
Expected behaviour:
Output.status.active
is set to false,Flow.status.active
is set to false. Output should reference the error message in its status, and Flow should get, if there was a single output configured in it,status.active: false
too.Steps to reproduce the bug:
Environment details:
/kind bug
The text was updated successfully, but these errors were encountered: