Restarting integration runtime pods

If you want to restart your integration runtime pods, for example, to pick up a new mounted secret, you can do so by adding an annotation to the 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 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.template.spec.metadata.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: IntegrationRuntime
metadata:
  labels:
    backup.appconnect.ibm.com/component: integrationruntime
  name: ir-01-quickstart
  namespace: ace
spec:
  license:
    accept: true
    license: <LICENSE-IDENTIFIER>
    use: AppConnectEnterpriseProduction
  template:
    spec:
      containers:
        - name: runtime
          resources:
            requests:
              cpu: 300m
              memory: 368Mi
      metadata:
        annotations:
          restart: 05/12/2025@11:36am
  barURL:
    - 'https://db-01-quickstart-dash.ace:3443/v1/directories/CustomerDatabaseV1?a0f0c53f-e51e-44d2-91c9-e524569e33c6'
...