Chapter 5. Development preview
Developer Preview versions are provided to expose features from upstream communities for use by early adopters and integrators to explore and interact with new capabilities in advance of their possible inclusion in a Red Hat product offering. For more information, see link Developer Preview Support Scope.
- Restricted mode
-
In 7.13, the
ActiveMQArtemisCR supports a new attribute,spec.Restricted. If this attribute is set toTrue, an empty embedded broker is deployed. You can configure this broker by using thebrokerPropertiesattribute in theActiveMQArtemisCR. To secure end-to-end communication the broker requires a public key infrastructure (PKI). You can use cert-manager to generate the TLS certificates for the PKI. - Self-provisioning plugin
- The self-provisioning plugin is a dynamic plugin for the OpenShift Console. The plugin adds a new broker workload type to the OpenShift console that allows you to create and manage broker deployments on OpenShift. A Jolokia API server is included with the self-provisioning plugin. The API server builds requests made in the self-provisioning plugin UI and send them to the Jolokia endpoint on the broker. The self-provisioning plugin and the Jolokia API server are available on the Software Downloads page for AMQ Broker 7.13 releases:
You can install the self-provisioning plugin only on a cluster that is running OpenShift 4.16 or later.
Complete the following steps to install the Jolokia API server and the self-provisioning plugin on your OpenShift cluster.
- Ensure that the AMQ Broker Operator and the cert-Manager Operator for OpenShift are installed on the cluster.
- Log in to your OpenShift cluster by using the OpenShift command-line interface (CLI).
- In your web browser, navigate to the Software Downloads page for AMQ Broker 7.13 releases.
- Next to the AMQ Broker 7.13.0 Jolokia API Server installation files, click Download.
- Next to the AMQ Broker 7.13.0 self-provisioning plugin installation files, click Download.
Move the downloaded archives to a new directory. The following example moves the archive to a directory called ~/broker/spp.
$ mkdir ~/broker/spp $ mv amq-broker-jolokia-api-server-7.13.0-install-rhel9.zip ~/broker/spp $ mv amq-broker-self-provisioning-plugin-7.13.0-install-rhel9.zip ~/broker/sppExtract the contents of the archives. For example:
$ cd ~/broker/spp $ unzip amq-broker-jolokia-api-server-7.13.0-install-rhel9.zip $ unzip amq-broker-self-provisioning-plugin-7.13.0-install-rhel9.zipSwitch to the directory that was created when you extracted the Jolokia API server archive.
$ cd amq-broker-jolokia-api-server-7.13.0-installRun the script to install the Jolokia API server:
// AsciiDocDITA.BlockTitle, warning, Block titles can only be assigned to examples, figures, and tables in DITA. ./deploy.shSwitch to the directory that was created when you extracted the self-provisioning plugin archive.
$ cd ../amq-broker-self-provisioning-plugin-7.13.0-installRun the script to install the self-provisioning plugin:
// AsciiDocDITA.BlockTitle, warning, Block titles can only be assigned to examples, figures, and tables in DITA. ./deploy-plugin.sh-
Verify that the pods for the Jolokia API server and the self-provisioning plugin are running in the
activemq-artemis-jolokia-api-serverand theactivemq-artemis-self-provisioning-pluginnamespaces.
For information about how to try out the plugin see the self-provisioning plugin readme file.