Have AMQ Broker use keystores and truststores created by cert-manager

Solution Verified - Updated -

Issue

Since OpenShift 4.10 Red Hat offers a supported version of the cert-manager operator. With this operator, you can create TLS secrets from Certificate custom resources that can optionally include keystore.jks and truststore.jks files. For the password of this keystore and truststore, a separate secret is used. The TLS secret that is configured in a TLS-enabled acceptor of an ActiveMQ Artemis custom resource requires a different setup, however. In an AMQ Broker TLS secret the files must be named broker.ks and client.ts and the passwords of this keystore and truststore must be included in the same secret. Can the AMQ Broker operator be adapted to support TLS secrets generated by cert-manager?

Environment

  • Red Hat AMQ
    • 7.10.0

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