RHACS Central shows "no such host" error after being migrated to different namespace

Solution Verified - Updated -

Issue

  • After moving the Central component of Red Hat Advanced Cluster Security (RHACS) into a custom namespace, there are the following errors shown in the logs:

    Warning alert:failed to determine Scanner V4 cert expiry errors: [failed to contact scanner at scanner-v4-matcher.stackrox.svc:8443: unable to establish a TLS-enabled connection: dial tcp: lookup error: no such host, failed to contact scanner at scanner-v4-indexer.stackrox.svc:8443: unable to establish a TLS-enabled connection: dial tcp: lookup error: no such host]

Environment

  • Red Hat Advanced Cluster Security for Kubernetes (RHACS) 4.8

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