Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

PowerProtect Data Manager 19.10 Kubernetes User Guide

YAML configuration files

The YAML configuration files form the core of each application template. These files serve as user-configurable inputs to the process of deploying application templates for namespaces.

The YAML files help you quickly deploy application templates with similar properties by reusing the same YAML file for multiple databases across different namespaces. The CLI package comes with sample configuration files for each supported type of database application. You can copy and then customize these files for your environment.

Each sample from the CLI package contains examples of different application actions, such as selectors that filter by name and by regular expression. The CLI package also comes with a readme file for additional information, including the expected environment variables for each default deployment. Different application types may use different terminology.

The samples explicitly spell out the quiesce and unquiesce command strings, they do not use the default commands that are described in a subsequent topic. This method is normal for templates that are deployed to a specific namespace. If you intend to create a template for deployment to the PowerProtect namespace, you must replace the command strings with the default commands.

You can start building your own command strings by copying the samples and customizing as necessary to change the values. Customization can include changing the location of the lock file, changing the sleep counts, and so forth. You are responsible for any changes to the default command strings.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\