Restarting integration server or integration runtime pods

If you want to restart your integration server or integration runtime pods, for example, to pick up a new mounted secret, you can do so by adding an annotation to the integration server or integration runtime custom resource (CR). The annotation is added to the deployment, which then triggers a rolling restart of the associated pods in accordance with the update strategy.

To trigger a rolling restart of your integration server pods, you can use the spec.annotations.restart parameter.
```
spec:
  annotations:
    restart: value
```
To trigger a rolling restart of your integration runtime pods, you can use the spec.template.spec.metadata.annotations.restart parameter.
```
spec:
  template:
    spec:
      metadata:
        annotations:
          restart: value
```

This custom annotation is merged with the default (generated) annotations.

The following example illustrates how you can use the spec.annotations.restart parameter for integration servers 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: AppConnectEnterpriseProduction
  annotations:
    restart: '05/12/2021@11:36am'
  pod:
    containers:
      runtime:
        resources:
          limits:
            cpu: 300m
            memory: 368Mi
          requests:
            cpu: 300m
            memory: 368Mi
  barURL:  https://db-quickstart-dash:3443/v1/directories/CustomerDatabaseV1?b6dff5ca-5869-4edd-92d3-4d6231995472
...