Applying the custom resources for Automation Decision Services

What you apply in the custom resources (CR) for Automation Decision Services depends on your target Kubernetes cluster. You apply certain choices available in the storage classes.

1. Run the following command to verify that Automation Decision Services has a valid yaml file, and it conforms to the expected grammar:

   kubectl apply -f <ads_cr_path> --validate='strict'

   Remember: Running the command does not prevent certain errors such as unintentional duplications of a section.
2. When you finish applying your CR, you can view the progress of the installation by checking your CR status.
   For example, you can run the following command:

   kubectl get ads ads-standalone -n ads -o yaml -o go-template='{{range .status.conditions}}CONDITION: {{.type}}{{"\n"}}  STATUS: {{.status}}{{"\n"}}  MESSAGE: {{.message}}{{"\n"}}{{end}}'
   CONDITION: Running
     STATUS: False
     MESSAGE: 
   CONDITION: Ready
     STATUS: True
     MESSAGE: 
   CONDITION: PostgresInstalled
     STATUS: True
     MESSAGE: 
   CONDITION: DesignerInstalled
     STATUS: True
     MESSAGE: 
   CONDITION: RuntimeInstalled
     STATUS: True
     MESSAGE: 

   Note: Running indicates whether the Automation Decision Services operator is reconciling. Its status is True if it is processing a CR change, or it was fired by a Kubernetes event it watches (like a secret modification). False is expected when no reconciliation is ongoing.

   You might have some expected transient errors (unknown type errors) reported in the status while the foundational services operators and custom resource definitions (CRD) are pulled and started. Then, ZenService starts and the Automation Decision Services status reports its progress.

   For more information about the CR statuses, see Custom resource statuses.

   Tip:

   The Automation Decision Service status is set to ready when all Automation Decision Services components have at least one pod ready. It can take about 30 minutes for the first start before it's ready.

   When you run the following command, you can wait until the Automation Decision Services installation status becomes ready:

   kubectl wait ads ads-standalone -n ads --for=condition=Ready=True --timeout=30m