Starting and Stopping a Containerized MID Server in a Red Hat OpenShift on IBM Cloud Environment Creates a New MID Server with Same NameIssue Issue: Starting and Stopping a Containerized MID Server in RH OpenShift on IBM Cloud Environment Creates a New MID Server with Same Name. If use of the new mid server is continued there will be encryption errors. If the MID Server has not been validated yet then it will have to be rekeyed.If the MID Server has already been validated then it will need to be invalidated.ReleaseRelease: Rome and later releases Environment: Red Hat OpenShift on IBM Cloud/ CirrusCauseIf a Containerized MID Server is Stopped and Started in an OpenShift on IBM Cloud/Cirrus environment a new Container will be created and all configuration updates, keystore files, synced files, and changes in the work folder will be gone.ResolutionThe current workaround is to persist the MID Servers agent directory and it's contents to the containers Volume. Please see OpenShift Documentation on "Using volumes to persist container data" https://docs.openshift.com/container-platform/4.10/nodes/containers/nodes-containers-volumes.html Note: From security perspective, customers will need to check and make sure to keep the persisted data secure. Additionally the agent folder will need to be removed manually on the persistent volume when the MID Server is retired.