-
Story
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
Create CR with tihs bit:
console: expose: true sslEnabled: true secret: secret
Don't create a secret named "Secret".
In this case, SS is created properly and is in state "Ready 0/1" for up to 3-5 minutes before inevitably crashing with "keystore is not valid" error message.
While this error is indeed correct, its not very descriptive and comes too late in the life cycle of Broker.
This kind of situation should be caught in init container (i.e. init container should check if secret supplied a) exists b) is valid for use with java/broker)
- is incorporated by
-
ENTMQBR-7643 AMQ Broker Operator should verify the validity of ssl secrets on Openshift before updating/creating brokers
- Closed