Deployment requirements checklist

Master nodes

Check the overall deployment sizing requirements
for your containerized environment such as total
number of servers, total number of CPU,
memory, and disk space.

We do not provide sizing guidelines for master
nodes.
You can configure the master nodes based on
your environment requirements.

Master node disk space

Master nodes must have a minimum of 150GB
of free disk space.

Worker nodes

Check the overall deployment sizing requirements
for your containerized environment such as total
number of servers, total number of CPU, memory,
and disk space.

Sizing-and-scalability-considerations

Worker node disk space

Worker nodes must have a minimum of 100GB
of free disk space.

Storage

High performance of Kubernetes Persistent
Volume Disk is essential for the overall system
performance. 
Persistent Volume Disk requires block and NFS
storage.

We support a Bring-Your-Own-Storage model for
Kubernetes Persistent Volumes.

Sizing-and-scalability-considerations

Persistent Volume Claim requirements

We recommend that you use solid-state drive (SSD).

Important: PVc storage is mandatory for ITOM
implementation with a small requirement NFS. 

Run IOSTAT or equivalent disk
performance tool.

Performance should be as per BMC's recommendation.

System-requirements

Run the following command to check if
storage is in 'Bound' state:
kubectl get pv -o wide

Storage should be in 'Bound' state.

Operating System

Preparing-for-deployment

Discuss with system administrator of
the Operating Systems.

Discuss with system administrator.

High Availability (HA) and Disaster Recovery (DR)

Disk storage

Harbor registry

Install Harbor registry and set up SSL.

We recommend you deploy the Harbor registry
on a different system than the Kubernetes cluster.

Registry the Harbor registry with DNS and
configure it to use SSL.

Setting-up-a-Harbor-registry-in-a-local-network-and-synchronizing-it-with-BMC-DTR

Docker

Install Docker Compose version 1.29.2 on Harbor
Server.

Email Engine

The Common Services script
(deployment-manager.sh) attempts to connect
to an SMTP server and validates login.
The SMTP server is required to activate
a tenant through email.

We support all SMTP server types that can
communicate with the cluster.

A valid SMTP server is required for Production.
If you are running a POC or a Demo system
you might use the SMTP Sink process to
generate the activation email in a text file
on the Server.

Security Certificates

Firewall Ports

Network-ports

All names are resolved.

Firewall policies

Update your firewall policies to enable access to
BMC DTR.
Use the following fully qualified domain names:

• containers.bmc.com
• containers-glb.bmc.com
• containers-irl.bmc.com
• containers-msr-irl.bmc.com

Platform Software

Configure Static IP for Kubernetes environment,
on all master and worker nodes.

Static IP is recommended for easy LB
configuration and DNS entries.

Run the following command:
cat /etc/sysconfig/network-
scripts/ifcfg-ens<ethnum>

TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=static
IPADDR=<IP that is assigned>

DNS and URL Formation

Preparing-for-deployment

nslookup okd-tms.pe.example.com

Server:  gtm-prod-usa-phx-01-idns.example.com
Address:  xxx.xxx.xxx.xxx

Name:    loadbalancer-vip.example.com
Address:  xxx.xxx.xxx.xxx
Aliases:  okd-tms.pe.example.com

Load balancer

Configure the load balancer.

F5 load balancer and other
load balancers are supported.

Load-balancer-requirements

The following load balancer

SSL methods are supported:

• SSL Offloading at the
  load balancer
• SSL Passthrough to offload
  at the Ingress Controller
• SSL Full Proxy

Allow X-Forwarded- Headers
Upstream of Ingress.

Make sure that you
configure the following headers
for SSL Offloading at the
load balancer:

    X-Forwarded-Proto—https
    X-Forwarded-Host
    X-Forwarded-Port—443

Make sure you set the following parameters:

• LB_HOST
• TMS_LB_HOST
• MINIO_LB_HOST
• MINIO_API_LB_HOST
• KIBANA_LB_HOST 
• TMS

Load-balancer-requirements

A network administrator must validate
the parameters on a load balancer. 

After the ingress controller is configured, if you browse to the URLs, you must get 'default backend -404' error.

Monitor

Configure a forward proxy for Patrol Agents, if used.

Container

System-requirements

Functional

Test simple pod deployment.

Make sure that the Kubernetes cluster with master and worker nodes are fully functional before installation.

Run the following command to test
the deployment:

Make sure the pods

are in a running state and deployed across the nodes.

Ingress

Nginx Ingress controller is used to distribute the load between the services.

Review the supported Ingress controller versions and the parameter value requirements in the nginx-configuration configmap.

System-requirements

Run the following command to 
check the version of the ingress controller:
kubectl exec -it -n internet-ingress internet-ingress-controller-5vzrv -- /nginx-ingress-controller --version

Create a sample Ingress resource and test to make sure it's functioning with the load balancer.

Ingress parameters

Review parameter value requirements in the nginx-configuration configmap in the ingress-nginx namespace:

enable-underscores-in-headers—true
proxy-body-size—256m
proxy-connect-timeout—300
proxy-read-timeout—600
proxy-send-timeout—600
use-forwarded-headers—true

server-name-hash-bucket-size       1024
ssl-redirect        false

Run the following command:
kubectl describe cm nginx-configuration 
-n ingress-nginx

Helm

KUBECONFIG

KUBECONFIG must be configured to point to the Kubernetes cluster on the installation workstation.

System-requirements

Platform software

Verify that all nodes are in ready state.

For Kubernetes, run the command on the node
where kubectl is installed:
kubectl get nodes -n namespace

For Openshift, run the command where the OC
CLI is installed:
oc get nodes -n namespace

All nodes must be in ready state.

OpenShift only

For all the product components, make sure that you increase the number of threads to 4096 per node so that sufficient threads are available to the processes running in the containers

Deploying the ingress controller for OpenShift

Deploying-and-configuring-the-ingress-controller-for-OpenShift-or-Kubernetes

OpenShift cluster must have access to the NGINX Ingress Controller or Operator.

Deploying-and-configuring-the-ingress-controller-for-OpenShift-or-Kubernetes

Run the following commands:

kubectl get ns
kubectl get pod -n OpenShift-
ingress-operator

OpenShift-ingress Active 20d
OpenShift-ingress-operator Active 20d

NAME READY STATUS RESTARTS AGE
ingress-operator-7f6bf4f94b-bzrv5 2/2 Running 0 20d

Preparing-for-deployment

Docker 

Downloading-the-deployment-manager

Accessing-container-images

Software is downloaded from BMC DTR to local Harbor registry.

Snapshot

NA

Confirm if an action is taken.
Yes or No

Make sure you have deployed the latest version of PATROL Agents.

Health Check Tool

All checks must pass before proceeding with the installation.