Skip to content

fix: add in-cluster auth fallback for Kubernetes provider#5580

Open
PoornaChandra2005 wants to merge 1 commit intokeephq:mainfrom
PoornaChandra2005:bounty-k8s-auth
Open

fix: add in-cluster auth fallback for Kubernetes provider#5580
PoornaChandra2005 wants to merge 1 commit intokeephq:mainfrom
PoornaChandra2005:bounty-k8s-auth

Conversation

@PoornaChandra2005
Copy link

Fixes #5526

This PR adds a fallback to in-cluster configuration for the Kubernetes provider. If api_server or token are not provided, Keep will now automatically attempt to use the service account token mounted inside the cluster.

This enables seamless operation when Keep is deployed as a pod within the Kubernetes cluster.

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Feb 7, 2026

Target branch is not in the allowed branches list.

@dosubot dosubot bot added size:M This PR changes 30-99 lines, ignoring generated files. Bug Something isn't working Provider Providers related issues labels Feb 7, 2026
@vercel
Copy link

vercel bot commented Feb 7, 2026

@PoornaChandra2005 is attempting to deploy a commit to the KeepHQ Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Something isn't working Provider Providers related issues size:M This PR changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[➕ Feature]: Add support for in-cluster authentication to the Kubernetes provider

1 participant