Automation is opt-in. Automation is disabled by default and enabled by you. When you enable automation, RealTheory can make configuration changes within the scope and parameters of your automation profiles, including any default values that you have not changed.
What You Must Do to Opt In
RealTheory will not make any changes to workloads in a cluster until you complete all of the following. You control each one.
| Requirement | What it does | Where you set it |
|---|---|---|
| You make the cluster automation-ready | Gives the RealTheory Collector permission to change workloads in that cluster. | When you generate the Collector deployment YAML. See Making a Cluster Automation-Ready. |
| You create an Automation Profile that defines the scope of changes | Defines which workloads RealTheory can change, and how. | Settings > Automation > Workloads > Automation Profiles. See Automation Profiles Explained. |
| You assign the profile to the cluster | Applies the profile to the cluster directly, through an Automation Policy, or as the default profile. A default profile applies to every automation-ready cluster that no policy or direct assignment covers, within the cluster access of the profile's owner. | See Creating an Automation Profile, Creating an Automation Policy, and Setting the Default Automation Profile. |
| You turn on automation | Automation is off by default. RealTheory makes changes only while automation is on. | Use Enable automation at Settings > Automation > Workloads > Automation Profiles or Automation Policies. Both views change the same account-wide setting. |
Scope and Parameters
The scope of automation is the set of workloads that RealTheory can change. Scope has two parts, and automation changes only the workloads that both parts allow:
- The profile decides which clusters and workloads are in scope.
- Assignment decides which clusters the profile is attached to, through a policy, a direct assignment, or the default.
Each part is also limited by its owner's cluster access.
The parameters are the guardrails in each profile, for example how large a change can be and how often automation can change a workload.
See Automation Profile Guardrails for the full set of guardrails.
What Happens When You Turn Automation On or Off
Users with the sys_admin or automation_admin role can turn automation on or off.
If you have assigned profiles to automation-ready clusters, turning automation on lets RealTheory apply changes to the workloads in those clusters. Turning automation off preserves your profiles and policies for future use. The new setting can take a few minutes to take effect.
Important: Turning automation off does not stop a change that is already in progress.
Note: While automation is off, you can still create and edit profiles and policies, for example to correct a configuration before you turn automation back on.
See Also
Automation Explained
Automation Profiles Explained
Automation Policies Explained
Automation Owners Explained
Making a Cluster Automation-Ready
Rolling Back an Automation Change