Skip to main content
Version: 2.11

OCP Cluster Prerequisites

Before you add an OCP cluster to Portworx Backup, ensure that the following prerequisites are met:

  • Stork is installed on all application clusters.

  • The OCP cluster is available over network.

Troubleshooting in OCP clusters​

1. Activity timeline data loss​

If you see any data loss in activity timeline of Portworx Backup dashboard after you restart the pods, then you need to maintain persistent volumes for Prometheus logs for openshift-user-workload-monitoring namespace:

kind: ConfigMap
apiVersion: v1
metadata:
  name: user-workload-monitoring-config
  namespace: openshift-user-workload-monitoring
data:
  config.yaml: 
    alertmanager:
      enabled: true 
      enableAlertmanagerConfig: true 
    prometheus:
      volumeClaimTemplate:
        spec:
          storageClassName: <storage-class-name>
          resources:
            requests:
              storage: 10Gi

For more information on troubleshooting this data loss issue in timeline activity, refer to Prometheus documentation.

Refer Dashboards for more information on activity timeline data.

2. Timeout error in Portworx Backup web console​

If you see timeout error in Portworx Backup web console on OCP clusters, you can increase OCP route timeout duration. For more information, on how to increase OCP route, refer to Configuring route timeouts.


Related topic:

Last updated on