OpenShift Platform issues
OCP monitoring containers fail to start
OCP and BB monitoring conflict with each other
For example, many OCP containers fail to start and so get stuck in perpetual restart loops:
- console-operator
- oath-apiserver
- packageserver
- authentication-operator
Another issue is that when installing alertmanager with helm, it shows this error, which appears to conflict with pre-existing CRDs created by OCP:
Helm install failed: unable to build kubernetes objects from release manifest: error validating "": error validating data:
[ValidationError(Alertmanager.spec): unknown field "alertmanagerConfigNamespaceSelector" in com.coreos.monitoring.v1.Alertmanager.spec,
ValidationError(Alertmanager.spec): unknown field "alertmanagerConfigSelector" in com.coreos.monitoring.v1.Alertmanager.spec]
BigBang Version 1.15.2
We are aware that RH does not officially support custom installations of prometheus, however, BB has indicated RH is willing to provide limited assistance towards this end.