System requirements
BMC Software supports the following components:
Certified component matrix
The component matrix provides an overview of certified versions of NGINX Ingress Controller and F5 NGINX Plus, ensuring compatibility with Kubernetes and OpenShift environments.
NGINX Ingress Controller and Helm with Kubernetes orchestration
The certified versions of NGINX Ingress Controller and Helm with the Kubernetes orchestration platform are as follows:
Kubernetes | Ingress | Helm |
|---|---|---|
| 1.33 | 1.12.4 | 3.18 |
1.32 | 1.12.1 | 3.17 |
1.31 | 1.11.5 | 3.16 |
1.30 | 1.11.5 | 3.15 |
1.29 | 1.11.5 | 3.14 |
| 1.28 | 1.11.5 | 3.14 |
NGINX Ingress Controller and Helm with OpenShift orchestration
The certified versions of NGINX Ingress Controller and Helm with the OpenShift orchestration platform are as follows:
OpenShift | Ingress | Helm |
|---|---|---|
| 4.19 | 1.12.4 | 3.18 |
4.18 | 1.12.1 | 3.17 |
4.17 | 1.11.5 | 3.16 |
4.16 | 1.11.5 | 3.15 |
4.15 | 1.11.5 | 3.14 |
F5 NGINX Plus and Helm with Kubernetes orchestration
The certified versions of F5 NGINX Plus and Helm with the Kubernetes orchestration platform are as follows:
Kubernetes | F5 NGINX Plus | Helm |
|---|---|---|
| 1.33 | R34 | 3.18 |
| 1.32 | R34 | 3.17 |
| 1.31 | R30 | 3.16 |
| 1.30 | R30 | 3.15 |
| 1.29 | R30 | 3.14 |
| 1.28 | R30 | 3.14 |
Harbor repository requirements
The HTTPS protocol is required for the Harbor registry. For information about Harbor installation, see Installation and Configuration in Harbor documentation.
Make sure that your system meets the following requirements to access images from a local Harbor repository:
For information about setting up Harbor repository, see Setting up a Harbor registry in a local network and synchronizing it with BMC DTR.
Controller machine requirements
The controller machine supports the following Operating systems:
Operating System | Version |
|---|---|
Linux | 8.5 or higher |
Red Hat Enterprise Linux (RHEL)
| 8 or higher |
Ubuntu | 20.04.6 or higher |
Browser support
Namespaces
Create a namespace to deploy BMC Helix IT Operations Management.
For more information about creating a namespace, see Creating a namespace for deploying BMC Helix IT Operations Management.
Application-specific requirements for BMC Helix IT Operations Management applications
The following products/components are required for using BMC Helix IT Operations Management applications:
Requirements | Description |
|---|---|
BMC Discovery | The required version is 25.2 and later. BMC Discoveryis mandatory for all BMC Helix Operations Management and BMC Helix AIOps, but optional for BMC Helix Continuous Optimization deployments. Important: One instance of BMC Discovery can serve only one instance of BMC Helix Operations Management and BMC Helix Continuous Optimization deployments. You can either deploy a new instance of BMC Discovery or use an existing deployment (BMC Discovery version 25.1 only) not already used by another BMC Helix Operations Management instance. The following topics provide more information from the BMC Discovery documentation:
|
Swap | The swap must be turned off. |
IP configuration | All nodes must be configured with a static IP. |
SMTP | SMTP must be configured to enable email notifications, such as activation emails. |
| TLS |
Important |
1. In this documentation, NGINX Ingress Controller refers to the Open-Source NGINX Ingress Controller maintained by Kubernetes.
Where to go from here
Next task | |
|---|---|
Back to process |