Persistent Storage

Contact your Kubernetes cluster administrator to prepare a persistent volume that the Agents use for storage. The persistent volume ensures that job data and Agent state are kept during pod restarts. 

BMC recommends that you run multiple Agents on separate nodes in the namespace. The default is two Agents. To support multiple Agents, the storage class (and underlying storage technology) must support ReadWriteMany access mode (for example, a Storage Class for Amazon EFS). The recommended storage size is 5Gi per agent.

If you use an NFS Storage Class, ensure that the UID and GID, which are Storage Class parameters for dynamic provisioning, are set to the following values:

  • UID=1000  
  • GID=0

Note

There are other factors that you might need to consider when you choose a persistent volume or configure a new persistent volume. For example, if you want to support High Availability between clusters in the same geographical area or different geographical areas.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*