[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-9907":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":33,"readmeContent":34,"aiSummary":35,"trendingCount":16,"starSnapshotCount":16,"syncStatus":19,"lastSyncTime":36,"discoverSource":37},9907,"kube-prometheus","prometheus-operator\u002Fkube-prometheus","prometheus-operator","Use Prometheus to monitor Kubernetes and applications running on Kubernetes","https:\u002F\u002Fprometheus-operator.dev\u002F",null,"Jsonnet",7672,2048,61,165,0,5,33,2,71.73,"Apache License 2.0",false,"main",true,[26,27,28,29,30,31,32,7],"alerts","cluster-monitoring","dashboards","hacktoberfest","kubernetes","operator","prometheus","2026-06-12 04:00:47","# kube-prometheus\n\n[![Build Status](https:\u002F\u002Fgithub.com\u002Fprometheus-operator\u002Fkube-prometheus\u002Fworkflows\u002Fci\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fprometheus-operator\u002Fkube-prometheus\u002Factions)\n[![Slack](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fjoin%20slack-%23prometheus--operator-brightgreen.svg)](http:\u002F\u002Fslack.k8s.io\u002F)\n\n> [!WARNING]\n> Everything is experimental and may change significantly at any time.\n\nThis repository collects Kubernetes manifests, [Grafana](http:\u002F\u002Fgrafana.com\u002F) dashboards, and [Prometheus rules](https:\u002F\u002Fprometheus.io\u002Fdocs\u002Fprometheus\u002Flatest\u002Fconfiguration\u002Frecording_rules\u002F) combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with [Prometheus](https:\u002F\u002Fprometheus.io\u002F) using the Prometheus Operator.\n\nThe content of this project is written in [jsonnet](http:\u002F\u002Fjsonnet.org\u002F). This project could both be described as a package as well as a library.\n\nComponents included in this package:\n\n* The [Prometheus Operator](https:\u002F\u002Fgithub.com\u002Fprometheus-operator\u002Fprometheus-operator)\n* Highly available [Prometheus](https:\u002F\u002Fprometheus.io\u002F)\n* Highly available [Alertmanager](https:\u002F\u002Fgithub.com\u002Fprometheus\u002Falertmanager)\n* [Prometheus node-exporter](https:\u002F\u002Fgithub.com\u002Fprometheus\u002Fnode_exporter)\n* [Prometheus blackbox-exporter](https:\u002F\u002Fgithub.com\u002Fprometheus\u002Fblackbox_exporter)\n* [Prometheus Adapter for Kubernetes Metrics APIs](https:\u002F\u002Fgithub.com\u002Fkubernetes-sigs\u002Fprometheus-adapter)\n* [kube-state-metrics](https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fkube-state-metrics)\n* [Grafana](https:\u002F\u002Fgrafana.com\u002F)\n\nThis stack is meant for cluster monitoring, so it is pre-configured to collect metrics from all Kubernetes components. In addition to that it delivers a default set of dashboards and alerting rules. Many of the useful dashboards and alerts come from the [kubernetes-mixin project](https:\u002F\u002Fgithub.com\u002Fkubernetes-monitoring\u002Fkubernetes-mixin), similar to this project it provides composable jsonnet as a library for users to customize to their needs.\n\n## Prerequisites\n\nYou will need a Kubernetes cluster, that's it! By default it is assumed, that the kubelet uses token authentication and authorization, as otherwise Prometheus needs a client certificate, which gives it full access to the kubelet, rather than just the metrics. Token authentication and authorization allows more fine grained and easier access control.\n\nThis means the kubelet configuration must contain these flags:\n\n* `--authentication-token-webhook=true` This flag enables, that a `ServiceAccount` token can be used to authenticate against the kubelet(s). This can also be enabled by setting the kubelet configuration value `authentication.webhook.enabled` to `true`.\n* `--authorization-mode=Webhook` This flag enables, that the kubelet will perform an RBAC request with the API to determine, whether the requesting entity (Prometheus in this case) is allowed to access a resource, in specific for this project the `\u002Fmetrics` endpoint. This can also be enabled by setting the kubelet configuration value `authorization.mode` to `Webhook`.\n\nThis stack provides [resource metrics](https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fmetrics#resource-metrics-api) by deploying\nthe [Prometheus Adapter](https:\u002F\u002Fgithub.com\u002Fkubernetes-sigs\u002Fprometheus-adapter).\nThis adapter is an Extension API Server and Kubernetes needs to be have this feature enabled, otherwise the adapter has\nno effect, but is still deployed.\n\n## Compatibility\n\nThe following Kubernetes versions are supported and work as we test against these versions in their respective branches. But note that other versions might work!\n\n> [!NOTE]\n> In CI we will be testing only last two releases and main branch on a regular basis.\n\n| kube-prometheus stack                                                                      | Kubernetes 1.31 | Kubernetes 1.32 | Kubernetes 1.33 | Kubernetes 1.34 | Kubernetes 1.35 |\n|--------------------------------------------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|\n| [`release-0.15`](https:\u002F\u002Fgithub.com\u002Fprometheus-operator\u002Fkube-prometheus\u002Ftree\u002Frelease-0.15) | ✔               | ✔               | ✔               | x               | x               |\n| [`release-0.16`](https:\u002F\u002Fgithub.com\u002Fprometheus-operator\u002Fkube-prometheus\u002Ftree\u002Frelease-0.16) | x               | ✔               | ✔               | ✔               | x               |\n| [`release-0.17`](https:\u002F\u002Fgithub.com\u002Fprometheus-operator\u002Fkube-prometheus\u002Ftree\u002Frelease-0.17) | x               | x               | ✔               | ✔               | ✔               |\n| [`main`](https:\u002F\u002Fgithub.com\u002Fprometheus-operator\u002Fkube-prometheus\u002Ftree\u002Fmain)                 | x               | x               | ✔               | ✔               | ✔               |\n\n## Quickstart\n\nThis project is intended to be used as a library (i.e. the intent is not for you to create your own modified copy of this repository).\n\nThough for a quickstart a compiled version of the Kubernetes [manifests](manifests) generated with this library (specifically with `example.jsonnet`) is checked into this repository in order to try the content out quickly. To try out the stack un-customized run:\n\n* Create the monitoring stack using the config in the `manifests` directory:\n\n  ```shell\n  # Create the namespace and CRDs, and then wait for them to be available before creating the remaining resources\n  # Note that due to some CRD size we are using kubectl server-side apply feature which is generally available since kubernetes 1.22.\n  # If you are using previous kubernetes versions this feature may not be available and you would need to use kubectl create instead.\n  kubectl apply --server-side -f manifests\u002Fsetup\n  kubectl wait \\\n      --for condition=Established \\\n      --all CustomResourceDefinition \\\n      --namespace=monitoring\n  kubectl apply -f manifests\u002F\n  ```\n\nWe create the namespace and CustomResourceDefinitions first to avoid race conditions when deploying the monitoring components.\nAlternatively, the resources in both folders can be applied with a single command\n`kubectl apply --server-side -f manifests\u002Fsetup -f manifests`, but it may be necessary to run the command multiple times for all components to\nbe created successfully.\n\n* To teardown the stack:\n\n  ```shell\n  kubectl delete --ignore-not-found=true -f manifests\u002F -f manifests\u002Fsetup\n  ```\n\nThe [official documentation](http:\u002F\u002Fprometheus-operator.dev\u002Fdocs\u002Fgetting-started\u002Finstallation\u002F) contains the full version of this quick-start guide, and includes [instructions](https:\u002F\u002Fprometheus-operator.dev\u002Fkube-prometheus\u002Fkube\u002Faccess-ui\u002F) on how to access Prometheus, AlertManager, and Grafana.\n\n### minikube\n\nTo try out this stack, start [minikube](https:\u002F\u002Fgithub.com\u002Fkubernetes\u002Fminikube) with the following command:\n\n```shell\nminikube delete && minikube start --container-runtime=containerd --kubernetes-version=v1.33.1 --memory=6g --bootstrapper=kubeadm --extra-config=kubelet.authentication-token-webhook=true --extra-config=kubelet.authorization-mode=Webhook --extra-config=scheduler.bind-address=0.0.0.0 --extra-config=controller-manager.bind-address=0.0.0.0\n```\n\nThe kube-prometheus stack includes a resource metrics API server, so the metrics-server addon is not necessary. Ensure the metrics-server addon is disabled on minikube:\n\n```shell\nminikube addons disable metrics-server\n```\n\n## Getting started\n\nBefore deploying kube-prometheus in a production environment, read:\n\n1. [Customizing kube-prometheus](docs\u002Fcustomizing.md)\n2. [Customization examples](docs\u002Fcustomizations)\n3. [Accessing Graphical User Interfaces](docs\u002Faccess-ui.md)\n4. [Troubleshooting kube-prometheus](docs\u002Ftroubleshooting.md)\n\n## Documentation\n\n1. [Continuous Delivery](examples\u002Fcontinuous-delivery)\n2. [Update to new version](docs\u002Fupdate.md)\n3. For more documentation on the project refer to `docs\u002F` directory.\n\n## Contributing\n\nTo contribute to kube-prometheus, refer to [Contributing](CONTRIBUTING.md).\n\n## Join the discussion\n\nIf you have any questions or feedback regarding kube-prometheus, join the [kube-prometheus discussion](https:\u002F\u002Fgithub.com\u002Fprometheus-operator\u002Fkube-prometheus\u002Fdiscussions). Alternatively, consider joining [#prometheus-operator](https:\u002F\u002Fkubernetes.slack.com\u002Farchives\u002FCFFDS2Z7F) slack channel or project's bi-weekly [Contributor Office Hours](https:\u002F\u002Fdocs.google.com\u002Fdocument\u002Fd\u002F1-fjJmzrwRpKmSPHtXN5u6VZnn39M28KqyQGBEJsqUOk\u002Fedit#).\n\n## License\n\nApache License 2.0, see [LICENSE](https:\u002F\u002Fgithub.com\u002Fprometheus-operator\u002Fkube-prometheus\u002Fblob\u002Fmain\u002FLICENSE).\n","kube-prometheus 是一个用于通过 Prometheus 监控 Kubernetes 及其上运行的应用程序的项目。它集成了 Prometheus Operator、高可用 Prometheus 和 Alertmanager、Prometheus node-exporter 与 blackbox-exporter、Prometheus Adapter、kube-state-metrics 以及 Grafana 等组件，提供了一整套易于操作的 Kubernetes 集群监控解决方案。项目使用 Jsonnet 编写，能够生成 Kubernetes 清单文件、Grafana 仪表盘和 Prometheus 规则，并且预配置了收集所有 Kubernetes 组件指标的功能，同时提供了默认的仪表盘和告警规则。适用于需要全面监控 Kubernetes 集群及其应用的场景，特别是对于那些希望简化监控系统搭建过程并快速获得洞察力的运维团队来说非常有用。","2026-06-11 03:25:19","top_topic"]