Introducing Automic Automation Kubernetes Edition

This release introduces the Automic Automation Kubernetes Edition (AAKE).

This Automic Automation container-based model uses Kubernetes and Helm charts and can be used for deployments on self-hosted Kubernetes clusters as well as managed Kubernetes services provided by, for example, AWS, Azure, or Google Cloud Platform.

Important! Please note that we provide support and documentation for the deployment and configuration of AAKE on Kubernetes only and not for Platform-as-a-Service such as OpenShift.

The Automic Automation Kubernetes Edition is an additional deployment option and gives you the same functionality as regular on-premises system. However, it has many benefits:

  • It allows you to install a new Automic Automation system or migrate your existing system to an AAKE system by deploying the necessary components to on-premises systems or cloud-hosted clusters

  • It provides flexible deployment options

  • It significantly reduces the installation effort

  • It gives you the freedom to design your system using an on-premises, hybrid, or public cloud infrastructure

  • It caters to business operators who need on-demand capacity and rapid development cycles for their business-critical workloads

The AAKE offering can be downloaded from https://downloads.automic.com/ and comprises all core and container-specific components, installation customizations for Automic Automation and Automic Intelligent Remediation, and a number of Action Packs that are loaded by default.

For more information about the supported platforms, prerequisites, preparation tasks and the installation process, see:

The communication between the Automation Engine and the Java components as well as the TLS/SSL Agents (Java, Windows, and UNIX Agents) uses TLS/SSL through a secure WebSocket (WSS). However, you can keep using older versions of your Agents and non-TLS/SSL Agents. The new component TLS Gateway allows non-TLS/SSL Agents to connect to the Automation Engine.

In an on-premises system, these components establish a connection with the new Java communication process (JCP), which uses trusted certificates to prove its identity to other communication partners. For more information about the TLS/SSL implementation, the new JCP, and the TLS Gateway, see What's New in the Automation Engine.

Important! TLS/SSL Agents (in containers and on-premises) as well as the TLS Gateway, when used for the Automic Automation Kubernetes Edition, establish a connection to an ingress / HTTPS load balancer, which requires a certificate for authentication.

Make sure that address of the load balancer is defined on both sides: the Automation Engine and the Agent / TLS Gateway and that your HTTPS load balancer has the required certificates in place. For more information, see Connecting to AWI, the JCP and REST Processes Using an Ingress.

For more information about the TLS/SSL certificates, ingresses and the load balancers, see: