Yes, please contact BMC Support.

Yes, please contact BMC Support.

Yes, please contact BMC Support.

Yes, please contact BMC Support.

Yes, please contact BMC Support.

Yes, please contact BMC Support.

See,  Migrating PATROL Agents from TSOM to BHOM and Migrating PATROL Agents in the BMC PATROL Agent for BMC Helix Operations Management documentation.

See,  BMC PATROL Agent documentation.

See,  Monitoring solutions in BMC Helix Operations Management in the BMC Infrastructure Management-PATROL Repository documentation.

See, System requirements.

Yes, we have documented an example using Squid. However you can utilize your own forward proxy. Discuss it with your Network Administrator.

For more information, see  Configuring a Squid proxy server in the BMC PATROL Agent for BMC Helix Operations Management documentation.

Yes, for more information see Using custom CA signed certificates.

1. Create a certificate signing request (csr) file by using OpenSSL.
2. Submit the the file < your.domain.com >.csr to your CA and request for signed certificate.
3. Import the CA's reply.

Yes, for more information see  Success Subscriptions .

Yes, see  BMC Education Subscription Services ,  BMC Helix On-Premises IT Operations Management Container Deployment: Essential Subscription , and  BMC Helix On-Premises IT Service Management Container Deployment: Essential Subscription

See,  BMC Helix onprem installation health check tool .

High availability is achieved through Kubernetes, which uses virtual services to load balance application pods across the cluster.

High availability is enabled for all but the compact sized deployments using multiple pods for each service.

For more information about system usage profiles, see Sizing considerations.

The Nginx Ingress controller is used to route requests to the appropriate services and pods within the cluster. Network load balancing is used to distribute the load of incoming requests across multiple nodes.

Where appropriate both readiness and liveness probes are defined in BMC images.

No, currently only Ingress NGINX is supported.

BMC Helix Logging is not available if you install BMC Helix ITOM version 23.2.02 or upgrade to BMC Helix ITOM 23.2.02 from an earlier version.
For an alternate method to view logs, see Why is Helix Logging not available in ITOM Deployment version 23.2.02? .

BMC provides deployment software automation and does not support Webhooks or CI/CD pipelines.

BMC does not use "latest" tags and uses versions wherever possible.

BMC software supports air-gapped deployments from a local registry which has been synchronized with the BMC containers.bmc.com.

For more information, see Setting up a Harbor registry through a proxy connection for an air-gapped deployment.

We set default requests and limits for all services. 

Yes, see

Converting PATROL Agent Pconfig rules to Policy Managment

Migrating TSOM Infrastructure Policies to BHOM with the bhompolicymigrator

Migrating PATROL Agents from TSOM to BHOM

Managing BHOM with the bhomadmin toolkit

Yes, you must to do it manually.

Yes, all DNS aliases must be set up before the installation and should resolve to the network load balancer.

For more information, see Load balancer requirements.

For local testing purposes, we have used an F5 load balancer. 
You can use your existing vendor-specific load balancer. You must make sure the DNS resolution and lookups are working fine. 

For more information, see Load balancer requirements.

The Static IP is a requirement for the common services and not for BMC Discovery. 
To get Static IP reach out to the in-house IT team to generate or assign for the environment.
 
The IP requirements are for the load balancer and the DNS. If we have a Static IP then making and maintaining configuration changes becomes less cumbersome when compared to maintaining a DHCP setup. 

See, Network ports.

See, Network ports. 

See, Configuration file settings.

See, Example configuration files for BMC Helix Operations Management.

See, Example configuration files for BMC Helix Continuous Optimization.

See, Example configuration files for BMC Helix Intelligent Automation.

Yes, we do support a single Helix portal with BMC Helix ITSM and BMC Helix ITOM.

Please raise a case with BMC Support to help you confirm requirements.

We recommend that you update default passwords for VMs, databases, and products to be compliant with your security policy to prevent any security issues. 

Yes, we do. However, if you find any subsequent security vulnerabilities, please raise a case with BMC support.

We use our own canonical container images which use a bmcuser in the majority of cases. We will not be able to align with the base container images used by customers as these can vary widely.

For data layer services (such as Kafka, Postgres, and ElasticSearch), we use Community Edition containers which include all default users and libraries. We might amend these images if we identify security exceptions but otherwise, they are unaltered.

See, Sizing considerations.

Please contact BMC Account Manager.

See, Downloading the deployment manager.

No, BMC Helix ITOM does not utilize Jenkins to deploy the product.

No, we do not  provide a Docker manifest for container images.

Supported versions are detailed in the product documentation. You many encounter issues with unsupported versions.