代码拉取完成，页面将自动刷新
Project status: beta Not all planned features are completed. The API, spec, status and other user facing objects may change, but in a backward compatible way.
The Prometheus Operator for Kubernetes provides easy monitoring definitions for Kubernetes services and deployment and management of Prometheus instances.
Once installed, the Prometheus Operator provides the following features:
Create/Destroy: Easily launch a Prometheus instance for your Kubernetes namespace, a specific application or team easily using the Operator.
Simple Configuration: Configure the fundamentals of Prometheus like versions, persistence, retention policies, and replicas from a native Kubernetes resource.
Target Services via Labels: Automatically generate monitoring target configurations based on familiar Kubernetes label queries; no need to learn a Prometheus specific configuration language.
For an introduction to the Prometheus Operator, see the initial blog post.
The Prometheus Operator makes the Prometheus configuration Kubernetes native and manages and operates Prometheus and Alertmanager clusters. It is a piece of the puzzle regarding full end-to-end monitoring.
kube-prometheus combines the Prometheus Operator with a collection of manifests to help getting started with monitoring Kubernetes itself and applications running on top of it.
The stable/prometheus-operator helm chart provides a similar feature set to kube-prometheus. This chart is maintained by the community. For more information, please see the chart's readme
Version >=0.18.0 of the Prometheus Operator requires a Kubernetes
cluster of version >=1.8.0. If you are just starting out with the
Prometheus Operator, it is highly recommended to use the latest version.
If you have an older version of Kubernetes and the Prometheus Operator running, we recommend upgrading Kubernetes first and then the Prometheus Operator.
The Operator acts on the following custom resource definitions (CRDs):
Prometheus, which defines a desired Prometheus deployment.
The Operator ensures at all times that a deployment matching the resource definition is running.
ServiceMonitor, which declaratively specifies how groups
of services should be monitored. The Operator automatically generates Prometheus scrape configuration
based on the definition.
PodMonitor, which declaratively specifies how groups
of pods should be monitored. The Operator automatically generates Prometheus scrape configuration
based on the definition.
PrometheusRule, which defines a desired Prometheus rule file, which can
be loaded by a Prometheus instance containing Prometheus alerting and
recording rules.
Alertmanager, which defines a desired Alertmanager deployment.
The Operator ensures at all times that a deployment matching the resource definition is running.
To learn more about the CRDs introduced by the Prometheus Operator have a look at the design doc.
To automate validation of your CRD configuration files see about linting.
Note that this quickstart does not provision an entire monitoring stack; if that is what you are looking for see the kube-prometheus project. If you want the whole stack, but have already applied the bundle.yaml, delete the bundle first (kubectl delete -f bundle.yaml).
To quickly try out just the Prometheus Operator inside a cluster, run the following command:
kubectl apply -f bundle.yaml
Note: make sure to adapt the namespace in the ClusterRoleBinding if deploying in a namespace other than the default namespace.
To run the Operator outside of a cluster:
make
scripts/run-external.sh <kubectl cluster name>
To remove the operator and Prometheus, first delete any custom resources you created in each namespace. The operator will automatically shut down and remove Prometheus and Alertmanager pods, and associated ConfigMaps.
for n in $(kubectl get namespaces -o jsonpath={..metadata.name}); do
kubectl delete --all --namespace=$n prometheus,servicemonitor,podmonitor,alertmanager
done
After a couple of minutes you can go ahead and remove the operator itself.
kubectl delete -f bundle.yaml
The operator automatically creates services in each namespace where you created a Prometheus or Alertmanager resources, and defines three custom resource definitions. You can clean these up now.
for n in $(kubectl get namespaces -o jsonpath={..metadata.name}); do
kubectl delete --ignore-not-found --namespace=$n service prometheus-operated alertmanager-operated
done
kubectl delete --ignore-not-found customresourcedefinitions \
prometheuses.monitoring.coreos.com \
servicemonitors.monitoring.coreos.com \
podmonitors.monitoring.coreos.com \
alertmanagers.monitoring.coreos.com \
prometheusrules.monitoring.coreos.com
Ensure that you're running tests in the following path:
$GOPATH/src/github.com/coreos/prometheus-operatoras tests expect paths to match. If you're working from a fork, just add the forked repo as a remote and pull against your local coreos checkout before running tests.
make test-unit
minikube start --kubernetes-version=v1.10.0 --memory=4096 --extra-config=apiserver.authorization-mode=RBACeval $(minikube docker-env) && make image - build Prometheus Operator
docker image on minikube's dockermake test-e2ekind create cluster --image=kindest/node:<latest>. e.g v1.16.2 version.export KUBECONFIG="$(kind get kubeconfig-path --name="kind")"make image - build Prometheus Operator docker image locally.for n in "operator" "config-reloader"; do kind load docker-image "quay.io/coreos/prometheus-$n:$(git rev-parse --short HEAD)"; done - publish
built locally images to be accessible inside kind.make test-e2eMany files (documentation, manifests, ...) in this repository are
auto-generated. E.g. bundle.yaml originates from the Jsonnet files in
/jsonnet/prometheus-operator. Before proposing a pull request:
make generate-in-docker.If you find a security vulnerability related to the Prometheus Operator, please do not report it by opening a GitHub issue, but instead please send an e-mail to the maintainers of the project found in the OWNERS file.
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。
