You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 5, 2021. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: