After cluster installation, some required monitoring pods cannot get persistent volumes attached when using custom AWS KMS key
Issue
- After installing a Red Hat OpenShift on AWS by using a custom AWS KMS key, the
monitoring
operator is in DEGRADED state. - The pods
alertmanager-main
andprometheus-k8s
along with theirPersistent Volume Claims
fromopenshift-monitoring
namespace are onPending
state.
Environment
- Red Hat OpenShift Service on AWS [ROSA]
- 4.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.