How to fix cluster-monitoring-operator in OpenShift 3.11
Page content
Default install use an old image for cluster-monitoring-operator with imagestream false latanci alert problem.
Parts of the Openshift series
- Part1: Install Opeshift
- Part2: How to Enable Auto Approval of CSR in Openshift v3.11
- Part3: Add new workers to Openshift cluster
- Part4: Chane the certificates of the Openshift cluster
- Part5: LDAP authentication for Openshift
- Part6: Keycloak SSO authentication for Openshift
- Part7: Gitlab SSO authentication for Openshift
- Part8a: Ceph persistent storage for Openshift
- Part8b: vSphere persistent storage for Openshift
- Part9: Helm on Openshift
- Part10: Tillerless Helm on Openshift
- Part11: Use external docker registry on Openshift
- Part12: Secondary router on Openshift
- Part13a: Use Letsencrypt on Openshift
- Part13b: Install cert-managger on Openshift
- Part14: Create Openshift operators
- Part15: Convert docker-compose file to Opeshift
- Part16a: Opeshift elasticsearch search-guard error
- Part16b: Openshift: Log4Shell - Remote Code Execution (CVE-2021-44228) (CVE-2021-4104)
Export running deployment to yaml
oc project openshift-monitoring
oc get --export deployment/cluster-monitoring-operator -o yaml > cluster-monitoring-operator.yaml
Patch and deploy the yaml
sed -i -e "s|image:.*|image: quay.io/openshift/origin-cluster-monitoring-operator:v3.11
|" \
> cluster-monitoring-operator.yaml
oc apply -f cluster-monitoring-operator.yaml
curl -k -H "Authorization: Bearer `oc serviceaccounts get-token asb-client`" https://`oc get routes -n openshift-ansible-service-broker --no-headers | awk '{print $2}'`/osb/v2/catalog
oc delete deployment/prometheus-operator
oc delete statefulset/alertmanager-main
oc delete statefulset/prometheus-k8s
Config for new install
openshift_cluster_monitoring_operator_image=quay.io/openshift/origin-cluster-monitoring-operator:v3.11
