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 bucket
- How to debug failed Automation Suite installations
- How to disable TX 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
- Exploring Logs
OUT OF SUPPORT
Automation Suite Installation Guide
Last updated Nov 21, 2024
AWS Deployment Architecture
This page provides general guidance on deploying Automation Suite to Azure.
- A highly available architecture that spans two or more Availability Zones.
- A virtual private cloud (VPC) configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.
- In the public subnets:
- A Linux bastion host to control inbound SSH (port 22) access to Amazon Elastic Compute Cloud (Amazon EC2) instances in the private subnets.
- Security groups for fine-grained inbound access to bastion host instance.
- In the private subnets:
- An Amazon EC2 Auto Scaling group with Kubernetes server nodes. Nodes are hosted on Amazon EC2 instances running RedHat 8.3.
- An Amazon EC2 Auto Scaling group with Kubernetes agent nodes. Nodes are hosted on Amazon EC2 instances running RedHat 8.3
- A database subnet group for Amazon Relational Database Service (Amazon RDS) DB instances running SQL Server.
- An Application Load Balancer or a Network Load Balancer to balance 443 inbound traffic between all kubernetes nodes.
- An internal Network Load Balancer to balance 6443 (the kube API) and 9345 (the RKE2 registration address) traffic between the kubernetes server nodes.
- Security groups for fine-grained access to the Kubernetes server nodes, as well as the agent nodes.
- AWS Certificate Manager for domain registration with a Secure Sockets Layer certificate.
- Amazon Route 53 as Domain Name System provider to route traffic to the Application Load Balancer.
- Multiple AWS Identity and Access Management (IAM) roles granting access to various operations required during deployment and installation.
