-
Notifications
You must be signed in to change notification settings - Fork 181
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
OIDC Authentication for Alertmanager and Loki #712
Comments
You're right, it might imply a lot of changes, let me dig first |
Had a discussion out of band, long and short of it, going to try to extend the existing http client with OIDC auth instead of using the Loki or Alertmanager clients |
You mean the http client shared between the different outputs? If you do so, it means more than Loki and AlertManager will have the benefit, so their configs must be adapted either. |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh with Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue with Mark the issue as fresh with Provide feedback via https://github.com/falcosecurity/community. |
@poiana: Closing this 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-sigs/prow repository. |
Motivation
I'm trying to push outputs to Alertmanager and Loki, but cross-cluster traffic is authenticated via Service Accounts in OIDC.
Feature
Support OIDC clients in both Loki and Alertmanager outputs.
I'm happy to commit up a PR, but this is potentially a 'more involved' code change so I would like to discuss, scope and approach, and acceptance criteria.
The text was updated successfully, but these errors were encountered: