Must-Gather for Certified Container Installations

Product Release Details

Gather the following list of product related information:

IBM Sterling B2B Integrator or Sterling File Gateway Certified Container:
- Product release version.
- Chart version and details.
  Run the helm command to obtain the details:
```
helm show chart <path/to/b2bi-or-sfg-helm-charts>
```
- Image version and details.
  Identify the image tags for all the IBM Sterling B2B Integrator/IBM Sterling File Gateway images configured in the helm values override yaml file – b2bi/sfg, dbsetup, purge, resources.
  For each of the Sterling B2B Integrator/Sterling File Gateway images, run the command using docker or podman CLI tool to obtain the details:
```
podman inspect <image repo>:<image tag>
```
  or
```
docker inspect <image repo>:<image tag>
```
Product integrations with SSP, SEAS, Connect:Direct, ITXA, ITX, ICC, and others. Identify the integrated product release version details.

Gather the following list of container environment information:

Container Management Platform and Infrastructure Provider.
Identify the Kubernetes platform and infrastructure provider. The most commonly supported platforms are mentioned below:
- Kubernetes
  Managed service platforms:
  - Amazon Elastic Kubernetes Service (Amazon EKS)
  - Microsoft Azure Kubernetes Service (Microsoft AKS)
  - Google Kubernetes Engine (Google GKE)
  - IBM Cloud Kubernetes Service (IKS)
  On-premises or Self-managed platform:
  - On-prem Kubernetes cluster on VMware vSphere, OpenStack, BareMetal or any other platform.
- Red Hat OpenShift
  Managed service platform:
  - Red Hat OpenShift Dedicated (OSD)
  - Red Hat OpenShift Service on Amazon AWS (ROSA)
  - Microsoft Azure Red Hat OpenShift (ARO)
  - IBM Cloud Red Hat OpenShift Service (IBM ROKS)
  On-premises or Self-managed platform:
  - Red Hat OpenShift Container Platform (OCP)
Container Management Platform Version.
Identify the Kubernetes/OpenShift version. Run the command using the Kubernetes/OpenShift CLI tool to obtain the version:
- Kubernetes:
```
kubectl version
```
- OpenShift:
```
oc version
```
Helm version.
Run the command using helm CLI tool to identify the version:
```
helm version
```
Platform architecture
- AMD64
- ppc64le (IBM Power)
- S390x (IBM zSystems)
Platform cluster details
- Number of worker nodes
- Number of master nodes (if self-managed)
- CPU, Memory, and Disk capacity for each of the worker nodes

Gather the following list of external services information:

Database: Identify the database vendor, version, and deployment model details for on-premises, self-managed on cloud or database as a service (DBaaS) on cloud, and so on.
IBM MQ: Identify the MQ server version and deployment model details - on-premises, container-based, operator-based or service on the cloud.
Storage: Identify the type and class of storage (File, Block or Object Store), IOPS, and provisioned size.

Gather the following list of product deployment information:

Configuration details:
- Helm chart values override configuration YAML (Mask IPs or any other sensitive data)
- Customer override configurations
- Tuning properties
Deployment details:
Capture an overview of all the relevant Kubernetes resources deployed as part of the product helm charts:
```
oc get pods,statefulset,jobs,pvc,pv,services,ingress,routes,networkpolicy,configmaps,secrets –n <namespace> -o wide  > deployment-resources.txt
```
Important: The above command only captures the secret names and not the details. Additionally, you can redact any internal IPs or any other sensitive data from the captured output before sharing that with support.