华为云 2c 4g安装3.2.0版本无法启动。如何解决？
Name: prometheus-k8s-0
Namespace: kubesphere-monitoring-system
Priority: 0
Node: <none>
Labels: app=prometheus
controller-revision-hash=prometheus-k8s-5475785cfc
prometheus=k8s
statefulset.kubernetes.io/pod-name=prometheus-k8s-0
Annotations: <none>
Status: Pending
IP:
IPs: <none>
Controlled By: StatefulSet/prometheus-k8s
Containers:
prometheus:
Image: prom/prometheus:v2.26.0
Port: 9090/TCP
Host Port: 0/TCP
Args:
–web.console.templates=/etc/prometheus/consoles
–web.console.libraries=/etc/prometheus/console_libraries
–config.file=/etc/prometheus/config_out/prometheus.env.yaml
–storage.tsdb.path=/prometheus
–storage.tsdb.retention.time=7d
–web.enable-lifecycle
–storage.tsdb.no-lockfile
–query.max-concurrency=1000
–web.route-prefix=/
Limits:
cpu: 4
memory: 16Gi
Requests:
cpu: 200m
memory: 400Mi
Readiness: http-get http://:web/-/ready delay=0s timeout=3s period=5s #success=1 #failure=120
Environment: <none>
Mounts:
/etc/prometheus/certs from tls-assets (ro)
/etc/prometheus/config_out from config-out (ro)
/etc/prometheus/rules/prometheus-k8s-rulefiles-0 from prometheus-k8s-rulefiles-0 (rw)
/prometheus from prometheus-k8s-db (rw,path=“prometheus-db”)
/var/run/secrets/kubernetes.io/serviceaccount from prometheus-k8s-token-w2gsv (ro)
config-reloader:
Image: kubesphere/prometheus-config-reloader:v0.43.2
Port: 8080/TCP
Host Port: 0/TCP
Command:
/bin/prometheus-config-reloader
Args:
–listen-address=:8080
–reload-url=http://localhost:9090/-/reload
–config-file=/etc/prometheus/config/prometheus.yaml.gz
–config-envsubst-file=/etc/prometheus/config_out/prometheus.env.yaml
–watched-dir=/etc/prometheus/rules/prometheus-k8s-rulefiles-0
Limits:
memory: 25Mi
Requests:
memory: 25Mi
Environment:
POD_NAME: prometheus-k8s-0 (v1:metadata.name)
Mounts:
/etc/prometheus/config from config (rw)
/etc/prometheus/config_out from config-out (rw)
/etc/prometheus/rules/prometheus-k8s-rulefiles-0 from prometheus-k8s-rulefiles-0 (rw)
/var/run/secrets/kubernetes.io/serviceaccount from prometheus-k8s-token-w2gsv (ro)
Conditions:
Type Status
PodScheduled False
Volumes:
prometheus-k8s-db:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: prometheus-k8s-db-prometheus-k8s-0
ReadOnly: false
config:
Type: Secret (a volume populated by a Secret)
SecretName: prometheus-k8s
Optional: false
tls-assets:
Type: Secret (a volume populated by a Secret)
SecretName: prometheus-k8s-tls-assets
Optional: false
config-out:
Type: EmptyDir (a temporary directory that shares a pod’s lifetime)
Medium:
SizeLimit: <unset>
prometheus-k8s-rulefiles-0:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: prometheus-k8s-rulefiles-0
Optional: false
prometheus-k8s-token-w2gsv:
Type: Secret (a volume populated by a Secret)
SecretName: prometheus-k8s-token-w2gsv
Optional: false
QoS Class: Burstable
Node-Selectors: kubernetes.io/os=linux
Tolerations: dedicated=monitoring:NoSchedule
node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Warning FailedScheduling 2m13s (x720 over 17h) default-scheduler 0/1 nodes are available: 1 Insufficient cpu.
