Last Modified: Feb 11, 2025
Affected Product(s):
BIG_IP_NEXT(CM) MA-CM
Known Affected Versions:
20.2.0, 20.2.1
Opened: Jul 08, 2024 Severity: 2-Critical
The Prometheus pod is stuck in a CrashLoopBackOff state with 2 out of 3 containers running.
Prior to the BIG-IP Next 20.3.0 release, instance telemetry data will be unavailable. Starting with the BIG-IP Next 20.3.0 release, there is no impact on functionality, as instance telemetry data is no longer stored in Prometheus. However, telemetry data for the BIG-IP Next Central Manager will not be available for debugging purposes. This does not affect any Central Manager functionality.
The Central Manager has accumulated a large amount of telemetry data.
SSH into the Central Manager as the admin user and execute the following commands: pvc_name="pvc/prometheus-pv-claim" pv_name="pv/$(kubectl get ${pvc_name} -o jsonpath='{.spec.volumeName}')" pod_name=$(kubectl get pod -l app.kubernetes.io/name=prometheus -o name) echo "apiVersion: v1 kind: PersistentVolumeClaim metadata: name: prometheus-pv-claim annotations: "helm.sh/resource-policy": keep labels: helm.sh/chart: prometheus-0.1.0 app.kubernetes.io/instance: prometheus app.kubernetes.io/name: prometheus app.kubernetes.io/version: "0.0.0" app.kubernetes.io/managed-by: Helm spec: storageClassName: local-path accessModes: - ReadWriteOnce resources: requests: storage: 10Gi" > pvc.yaml kubectl delete "${pv_name}" "${pvc_name}" "${pod_name}" kubectl apply -f pvc.yaml Confirm the Prometheus pod is running successfully and then execute this command: rm pvc.yaml
None