Automation Suite
2021.10
false
- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to Troubleshoot Services During Installation
- How to Uninstall the Cluster
- How to clean up offline artifacts to improve disk space
- How to Disable TLS 1.0 and 1.1
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bundle
- How to debug failed Automation Suite installations
- How to disable NIC checksum offloading
- Unable to run an offline installation on RHEL 8.4 OS
- Error in Downloading the Bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- SQL connection string validation error
- Failure After Certificate Update
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Cannot Log in After Migration
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Kinit: Cannot Find KDC for Realm <AD Domain> While Getting Initial Credentials
- Kinit: Keytab Contains No Suitable Keys for *** While Getting Initial Credentials
- GSSAPI Operation Failed With Error: An Invalid Status Code Was Supplied (Client's Credentials Have Been Revoked).
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis Probe Failure
- RKE2 Server Fails to Start
- Secret Not Found in UiPath Namespace
- ArgoCD goes into progressing state after first installation
- Unexpected Inconsistency; Run Fsck Manually
- Missing Self-heal-operator and Sf-k8-utils Repo
- Degraded MongoDB or Business Applications After Cluster Restore
- Unhealthy Services After Cluster Restore or Rollback
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Step 1.1: Creating the VM
Automation Suite Installation Guide
Last updated Apr 19, 2024
Step 1.1: Creating the VM
You need to have a resource group under your Azure subscription for running Automation Suite. If you want to use an existing one, you can skip this step and specify the resource group in the later steps.
- Go to the Azure portal.
- Search for Virtual Network from the home page and click Create.
All the machines that we provision should be part of this virtual network
- Go to the Azure portal.
- Type virtual machines in the search field.
- Under Services, select Virtual machines.
- In the Virtual machines page, select Create. The Create a virtual machine page opens.
You can configure the VM directly during the creation step under the Disks tab.
Important: Each machine needs to be added to the virtual network. For both single-node evaluation deployments or a multi-node HA-ready
production deployments, you need to create the virtual network. Each Azure VM resides in a Virtual Network (private network)
and the public IP is the way by which we are exposing it to external connections (internet).
Follow the steps below to create a new Virtual Network (or select the existing one) and Public IP address:
The next step is Step 1.2: Configuring the VM.