Restarting integration server pods
If you want to restart your integration server pods, for example, to pick up a new mounted secret, you can do so by adding an annotation to the integration server custom resource (CR). The annotation will be added to the deployment, which will trigger a rolling restart of the associated pods in accordance with the update strategy.
The following example illustrates how you can use the spec.annotations.restart parameter to specify a timestamp. The value of the timestamp has no significance other than to indicate a change from any existing value. The timestamp could serve as a useful reference for when the pods were last manually restarted.
apiVersion: appconnect.ibm.com/v1beta1
kind: IntegrationServer
metadata:
name: is-01-toolkit
namespace: ace
spec:
license:
accept: true
license: <VALID-LICENSE-ID>
use: AppConnectEnterpriseNonProduction
annotations:
restart: '05/12/2021@11:36am'
version: 12.0.1.0-r1
barURL: https://db-quickstart-dash:3443/v1/directories/CustomerDatabaseV1?b6dff5ca-5869-4edd-92d3-4d6231995472