feat: allow posting alerts service-to-service#5705
Merged
shahargl merged 3 commits intokeephq:mainfrom Mar 2, 2026
Merged
Conversation
|
@piekarski-mateusz is attempting to deploy a commit to the KeepHQ Team on Vercel. A member of the Team first needs to authorize it. |
dosubot
bot
added
the
size:L
Contributor
|
Target branch is not in the allowed branches list. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #5706
📑 Description
Allow trusted in-cluster services to POST alerts to Keep without requiring a Keep API key, using network-level authentication (e.g. Istio mTLS + AuthorizationPolicy) instead.
When the KEEP_ALLOW_MESH_ALERT_INGESTION environment variable is set to "true", requests to /alerts/event* that don't carry an API key or bearer token are accepted with the webhook role. Calling services can set the X-Service-Name HTTP header to identify themselves in logs and audit trails (defaults to "unknown").
✅ Checks
ℹ Additional Information
No breaking changes. The feature is entirely opt-in via an environment variable that defaults to "false". Existing deployments are unaffected.