The amq operator expects a secret with keys: broker.ks, client.ts, keyStorePassword and trustStorePassword.
oc create secret generic hq-tls-secret \
--from-file=broker.ks=server-ks.jks \
--from-file=client.ts=server-ks.jks \
--from-literal=keyStorePassword=secret \
--from-literal=trustStorePassword=secret
3rd party certificate manager, like jetstack, creates a secret with: keystore.jks, truststore.jks, and no passwords. It would be nice if operator allowed to specify those proeprties:
expose: true amqpMinLargeMessageSize: 204800 needClientAuth: false port: 5671 sslEnabled: true sslSecret: cert-broker-finance-secret sslBrokerKs: keystore.jks sslClientTs: truststore.jks sslTrustStorepasswordSecretRef: # Password used to encrypt the keystore key: password-key name: jks-password-secret sslKeyStorepasswordSecretRef: # Password used to encrypt the keystore key: password-key name: jks-password-secret wantClientAuth: false anycastPrefix: jms.queue. multicastPrefix: jms.topic.
- is duplicated by
-
ENTMQBR-5447 Certificate Manager to AMQ 7 on Openshift
-
- Closed
-
- relates to
-
-
- Verified
-
