Skip to content
View as markdown Ask ChatGPT Ask Claude

Deploy Automation Manager#

🔒 AutomationManager.Deploy

Overview#

This operation is used to deploy an existing Automation Manager.

Setup#

No specific setup is required other than to meet the preconditions of the transaction.

Note

If the Automation Manager requires storage resources, such as Persistent Volumes (PVs), they must be configured in advance, according to Configure Automation Manager Deployment. Otherwise, they won't be created automatically. If this happens, you’ll need to undeploy, update the configuration, and deploy again — which may cause issues if existing Persistent Volume Claims (PVCs) can’t be released due to permission restrictions.

Preconditions#

  • The Automation Manager exists in the system.
  • The Automation Manager has the Deployment Mode set as AutomaticDeploy.
  • The Automation Manager has the Deployment State different from Ready.

Sequence of Steps#

  1. Select Deploy to perform the operation. The current Deployment State will be changed to Ready.

Dependency#

This requires the installation of the Automation Manager Controller. This component will continuously query for new managers that are in a ready state, or Managers that were in a ready state but were undeployed. When the components receives differences it will deploy or undeploy new Manager instances.

Deployment Token#

When the Automation Manager Controller deploys an Automation Manager, it issues a Personal Access Token (PAT) for the integration user defined in the deployment configuration and stores it in a Kubernetes secret. The Automation Manager uses this token to authenticate with Critical Manufacturing MES:

  • The PAT belongs to the integration user and is named AMC-<timestamp>-<automation manager id>.
  • The secret is named am-user-<user account>-token-<automation manager id>, with both values sanitized to comply with Kubernetes naming rules. Each Automation Manager has its own secret.
  • The secret has an owner reference to the Deployment of the Automation Manager, so Kubernetes deletes the secret together with the Deployment.

Info

The controller issues a new token only when the secret does not exist. Undeploying the Automation Manager revokes the token and removes the secret, so the next deploy always issues a fresh token. This prevents a secret from outliving its token, for example after a release that is installed with a blank database. For more information, see Undeploy Automation Manager.