| Action | Container Based Steps |
| Reinstalling a product or component to resolve an issue. | Replace running container with a newly created one. |
| Editing a file stored on the host where the product runs. | Use configuration controls within the BMC product or use a Kubernetes configmap to provide access to a file stored outside of the container. |
| Collection of files (eg - logs and configuration) from the host for sending to BMC Support or further analysis. | Use Kubernetes/docker commands to copy files from a container to an external system or product specific tools such as the Support Assistant where available. |
| Installation and upgrades. | Refer to product documentation for the appropriate release. |
| Processes such as patch and hotfix deployments that include binary payloads. | Obtain an updated image from BMC and use to replace the running container. |
| Updates to third party components such as Java. | Obtain an updated image from BMC and use to replace the running container. |
| Actions that refer to Windows specific features such as Control Panel services or registry modifications. | BMC product containers are Linux based so the article contents may not be applicable if there is no Linux alternative. |
| Changes to the host operating system or network. | Use Kubernetes equivalents if applicable. |
| Use of host-based utilities or tools which interact with the host outside of the BMC Product. | Use Kubernetes equivalents if applicable. |
| Updating individual files which reside inside a container. | Obtain an updated image from BMC and use to replace the running container. |
| KA references a BMC utility which is not included as part of a product image. | Refer to product documentation or contact BMC Support for alternatives |