Skip to content
This repository has been archived by the owner on Nov 5, 2021. It is now read-only.

Add support for discovering Kubernetes targets. #273

Closed
manugarg opened this issue Aug 7, 2019 · 4 comments
Closed

Add support for discovering Kubernetes targets. #273

manugarg opened this issue Aug 7, 2019 · 4 comments
Assignees
Milestone

Comments

@manugarg
Copy link
Contributor

manugarg commented Aug 7, 2019

Based on the interactions with the Cloudprober users so far (over Github issues and in person), it's quite clear that cloudprober is used quite a lot within Kubernetes environment to monitor Kubernetes resources -- pods, services, etc. Adding auto-discovery support for Kubernetes resources will greatly help such setups. For example, we could auto-discover all pods having a particular label.

We should extend Cloudprober's RDS server to support Kubernetes resources. In RDS terms, "kubernetes" (or "k8s") will be the provider and supported resource types will be "pods", "services", "endpoints", etc.

@manugarg manugarg added this to the v0.10.6 milestone Aug 7, 2019
@manugarg manugarg self-assigned this Aug 16, 2019
@manugarg
Copy link
Contributor Author

manugarg commented Sep 9, 2019

Added framework support and pods as the first implementation in 34b261c.

@manugarg
Copy link
Contributor Author

Added support for endpoints as well: 808b8f9.

@manugarg
Copy link
Contributor Author

manugarg commented Nov 1, 2019

And, d832a46 adds support for services. I think all we need to do now is to write some documentation on how to use resource discovery in Kubernetes.

@manugarg
Copy link
Contributor Author

Closing this now. This feature is getting released in 0.10.6. We can do enhancements and other improvements through a separate issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant