Our great sponsors
-
-
kubeplus
Kubernetes Operator to create multi-instance SaaS from Helm charts using Kubernetes-native APIs
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
When you say capacity planning, can you elaborate on some use-case(s) that are being targeted with this feature? Is the idea that knowing the actual usage directly from the scheduler can help deployers, either from outside the cluster or in-cluster via GitOps, make informed decisions such as configuring node selectors on any future Pods? The reason I ask this is - in our project (KubePlus - https://github.com/cloud-ark/kubeplus ) we support Node selector policies at Helm chart level. This enables, for example, to create a Helm release on a specific worker node. Currently KubePlus is not using any metrics data to decide whether a particular node has enough spare capacity to accommodate the incoming Helm release. If the Pod metrics are available from the scheduler then we can correlate those with the nodes on which the Pods are running and then decide whether a node has enough remaining capacity to support the resources of the Helm release.