-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
AMQ 7.10.0.OPR.3.GA
-
None
-
False
-
None
-
False
-
Compatibility/Configuration, User Experience
-
0% To Do, 0% In Progress, 100% Done
The current CR's status of an ActiveMQArtemis manifest includes few information (pod's statuses) but anything related to services, routes, or the final version deployed. The operator creates many resources, but it is not clear to identify them unless you review the different components deployed in your OpenShift cluster. To avoid that, the CR's status could include that information in a very easy way to consume, allowing users to get the details and take action from there.
The following information could be great to have in the CR's status:
- Broker version deployed
- Status of the deployment, and last timestamp transition
- Services created, including the host, port, and protocol (if applies)
- Routes created, including the host, port, and protocol (if applies)
- Console information, host, and port
A sample approach could be similar to:
apiVersion: broker.amq.io/v1beta1 kind: ActiveMQArtemis metadata: name: dsp-amq-broker spec: acceptors: - expose: true name: core port: 61616 protocols: core - expose: true name: amqp port: 5672 protocols: amqp console: expose: true deploymentPlan: size: 1 image: placeholder upgrades: enabled: true minor: true version: 7.9.4 status: deploymentStatus: - lastTransitionTime: '2022-08-23T07:34:46.893Z' status: 'True' type: Ready version: 7.10.0 podStatus: ready: - dsp-amq-broker-ss-0 acceptors: - name: headless serviceBrokerUrl: 'dsp-amq-broker-hdls-svc.NAMESPACE.svc:61616' - name: core serviceBrokerUrl: 'dsp-amq-broker-core-0-svc.NAMESPACE.svc:61616' exposedBrokerUrl: 'dsp-amq-broker-core-0-svc-rte-NAMESPACE.apps.OPENSHIFT_DOMAIN:[80|443]' - name: amqp brokerUrl: 'dsp-amq-broker-amqp-0-svc.NAMESPACE.svc:5672' exposedBrokerUrl: 'dsp-amq-broker-ampq-0-svc-rte-NAMESPACE.apps.OPENSHIFT_DOMAIN:[80|443]' console: - name: dsp-amq-broker-ss-0 managementWeb: http://dsp-amq-broker-wconsj-0-svc-rte-NAMESPACE.apps.OPENSHIFT_DOMAIN:[80|443]'
- is cloned by
-
ENTMQBR-7650 [Docs] Extend CR's status with details of the broker deployed
- Closed
- is related to
-
ENTMQBR-6773 Provide feedback on the results of applying spec.brokerProperties
- Closed
-
ENTMQBR-7803 Add status condition to capture validity of CR
- Closed
-
ENTMQBR-8163 Operator address controller doesn't check for CR Status fields before trying to apply resources to the pod
- Closed
- relates to
-
ENTMQBR-8069 Failure to create Route is not indicated in CR Status
- Verified
-
ENTMQBR-6433 Add status to the ActiveMQArtemisAddress & ActiveMQArtemisSecurity CR
- Closed
-
ENTMQBR-8068 Duplicate ports in Acceptor definitions are regarded to be Valid according to CR Status
- Closed
- links to