KMM and KMM-Hub up to v1.1.0 cannot share the same namespace

Solution Verified - Updated -

Issue

When creating or updating Module or ManagedClusterModule issues, OpenShift returns error messages resembling the following:

Internal error occurred: failed calling webhook "vmanagedclustermodule.kb.io": failed to call webhook: Post "https://kmm-operator-hub-webhook-service.openshift-kmm.svc:443/validate-hub-kmm-sigs-x-k8s-io-v1beta1-managedclustermodule?timeout=10s": x509: certificate is valid for kmm-operator-webhook-service.openshift-kmm.svc, kmm-operator-webhook-service.openshift-kmm.svc.cluster.local, not kmm-operator-hub-webhook-service.openshift-kmm.svc

Metrics also appear to be inconsistent and unreliable.

Environment

This issue is reproducible on all OpenShift versions supported by KMM and KMM-Hub, when both operators in versions up to 1.1.0 are installed in the same namespace.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content