我正在尝试在全新的 k8s 集群中使用操作符创建 prometheus
我使用以下文件,
- 我正在创建一个命名空间监控
- 应用这个文件,就可以正常工作了
apiVersion: apps/v1beta2
kind: Deployment
metadata:
labels:
k8s-app: prometheus-operator
name: prometheus-operator
namespace: monitoring
spec:
replicas: 2
selector:
matchLabels:
k8s-app: prometheus-operator
template:
metadata:
labels:
k8s-app: prometheus-operator
spec:
priorityClassName: "operator-critical"
tolerations:
- key: "WorkGroup"
operator: "Equal"
value: "operator"
effect: "NoSchedule"
- key: "WorkGroup"
operator: "Equal"
value: "operator"
effect: "NoExecute"
containers:
- args:
- --kubelet-service=kube-system/kubelet
- --logtostderr=true
- --config-reloader-image=quay.io/coreos/configmap-reload:v0.0.1
- --prometheus-config-reloader=quay.io/coreos/prometheus-config-reloader:v0.29.0
image: quay.io/coreos/prometheus-operator:v0.29.0
name: prometheus-operator
ports:
- containerPort: 8080
name: http
securityContext:
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
nodeSelector:
serviceAccountName: prometheus-operator
现在我想应用这个文件(CRD)
apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
name: prometheus
namespace: monitoring
labels:
prometheus: prometheus
spec:
replica: 1
priorityClassName: "operator-critical"
serviceAccountName: prometheus
nodeSelector:
worker.garden.sapcloud.io/group: operator
serviceMonitorNamespaceSelector: {}
serviceMonitorSelector:
matchLabels:
role: observeable
tolerations:
- key: "WorkGroup"
operator: "Equal"
value: "operator"
effect: "NoSchedule"
- key: "WorkGroup"
operator: "Equal"
value: "operator"
effect: "NoExecute"
在我创建这些 CRD 之前
https://github.com/coreos/prometheus-operator/tree/master/example/prometheus-operator-crd https://github.com/coreos/prometheus-operator/tree/master/example/prometheus-operator-crd
问题在于Pod 无法启动(0/2),见下图。可能是什么问题呢?请指教
update
当我去参加舞会操作员的活动时,我看到以下错误creating: pods "prometheus-operator-6944778645-" is forbidden: no PriorityClass with name operator-critical was found replicaset-controller
, 任何想法 ?
您正在尝试引用operator-critical
优先级 https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#priorityclass。优先级类别决定 Pod 的优先级及其资源分配。
要解决此问题,您可以删除显式优先级类别(priorityClassName: "operator-critical"
)在两个文件中或创建operator-critical
class:
apiVersion: scheduling.k8s.io/v1beta1
kind: PriorityClass
metadata:
name: operator-critical
value: 1000000
globalDefault: false
description: "Critical operator workloads"
本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系:hwhale#tublm.com(使用前将#替换为@)