After cluster installation, some required monitoring pods cannot get persistent volumes attached when using custom AWS KMS key
- After installing a Red Hat OpenShift on AWS by using a custom AWS KMS key, the
monitoringoperator is in DEGRADED state.
- The pods
prometheus-k8salong with their
Persistent Volume Claimsfrom
openshift-monitoringnamespace are on
- Red Hat OpenShift Service on AWS [ROSA]
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.