Open praveenkumar opened 5 years ago
There is already a mojo doc and G-doc which contains that information, I am still not able to figure out even we do below operation the how come Prometheus
and other operator come back to cluster :(
$ oc get deployments --all-namespaces
$ oc scale --replicas=0 deployments/prometheus-operator -n openshift-monitoring
$ oc pod delete prometheus-k8s-0 -n openshift-monitoring
$ oc delete pod prometheus-k8s-1 -n openshift-monitoring
$ oc scale --replicas=0 deployments/grafana -n openshift-monitoring
$ oc scale --replicas=0 deployments/cluster-monitoring-operator -n openshift-monitoring
$ oc get pods -n openshift-monitoring
NAME READY STATUS RESTARTS AGE
alertmanager-main-0 3/3 Running 3 27d
alertmanager-main-1 3/3 Running 3 27d
alertmanager-main-2 3/3 Running 3 27d
cluster-monitoring-operator-59dcd6f846-52ctt 1/1 Running 0 36m
grafana-58456d859d-xfpjh 2/2 Running 0 36m
prometheus-k8s-0 0/6 Pending 0 36m
prometheus-k8s-1 6/6 Running 1 40m
prometheus-operator-845f967df4-8d5fr 1/1 Running 0 36m
Need to make a list of the current running operators on the fresh cluster and then also check the dependencies around it.