minikube VS Kube-state-metrics

With the containerized Node.js/Express API, I could run multiple containers, scaling to handle more traffic. Using a tool called minikube, we can easily spin up a local Kubernetes cluster to horizontally scale Docker containers. It was possible to keep one shared instance of the database, and many APIs were routed with an internal Kubernetes load balancer. - Source: dev.to / 29 days ago

Install Minicube - a tool that allows us to spin up a Kubernetes cluster in a local machine Run minikube start to start your Kubernetes cluster Run minikube dashboard to spin up a web-based user interface that allows you to manage your Kubernetes cluster. - Source: dev.to / about 1 month ago

Https://github.com/kubernetes/minikube for local learning that's lightweight. Source: about 1 year ago

Root@vagrant-ubuntu-trusty:~/docker-containers# docker imagesREPOSITORY TAG IMAGE ID CREATED SIZEdockercontainers\_jenkins latest bb1142706601 4 days ago 1.03GBdockercontainers\_sonar latest 3f021a73750c 4 days ago ... Source: about 1 year ago

Minikube (https://github.com/kubernetes/minikube) - based off of docker machine, uses driver for backend, so can use KVM, Vagrant, or Docker itself to bootstrap K8S cluster. Source: over 1 year ago

Those are entirely different types of data. You can get that from something like kube-state-metrics. Source: about 1 year ago

Kubernetes itself will not notify you, the way I've seen people do this, is to use something like kube-state-metrics or node_exporter, export that to Prometheus (or preferrably VictoriaMetrics because Prometheus is terrible IMO), and then setup alarms on that with alertmanager or equivalent, or just look at dashboards regularly with Grafana. Realistically I recommend only setting alerts on disk usage and... Source: about 1 year ago

We then have various other Metrics called Kubernetes Workload Metrics. These are the dashboards with names that start with “Kubernetes / Compute Resources / Workload”. These dashboards are specific to the services you are running. They take into account the Kubernetes Workloads in your various namespaces, using kube-state-metrics. For a closer look, check out otel_demo_app_k8s_dashboard.tf. - Source: dev.to / over 1 year ago

The first step to optimizing costs is gaining visibility into your costs using tools. Kubernetes provides a Metrics Server and kube-state-metrics that can give you the overall picture of resource utilization by your cluster. There are more tools that provide more granular breakdowns and provide dashboards with business metrics, infra cost, and alerting functionalities. Here are some strategies to optimize your... - Source: dev.to / over 1 year ago

If you have the kube-state-metrics + Prometheus with a sufficiently long retention time, then you could write a PromQL query based on the "kube_pod_created" metric to get the answer to your question. It might be possible with the metrics-server + Prometheus, but I think it would not count some pods that live less than one scrape interval. Source: over 1 year ago