Akka is a toolkit for building highly concurrent, distributed, and resilient message-driven applications for Java and Scala. Apache Pekko is a fork of Akka 2.6.x, prior to the Akka project’s adoption of the Business Source License.
Here are some examples how to backup the content of the Release installation on K8s cluster.
From 23.3 version, there are changes how is working answer to the question:
Prerequisites
You can install Release in an air-gapped environment disconnected from the public internet. This topic provides information about installing and upgrading Release in such environments using a Minikube cluster and a custom image registry. For other Kubernetes platforms, steps are similar to the ones listed here for Minikube as long as the custom image registry contains all the required images.
Note: Here is a basic setup for the AWS EKS cluster, use it as a guideline to create K8s cluster to have minimal K8s environment for Digital.ai Deploy or Release installation.
Note: Here is a basic setup for the Azure K8S cluster, use it as a guideline to create K8s cluster to have minimal K8s environment for Digital.ai Deploy or Release installation.
Note: Here is a basic setup for the GKE cluster, use it as a guideline to create K8s cluster to have minimal K8s environment for Digital.ai Deploy or Release installation.
Note: Here is a basic setup for the AWS Openshift cluster,
Important: Use these instructions to install Digital.ai Deploy or Release on a minikube multi-node cluster for testing or illustration purposes. Do not use these instructions to set up a production environment.
* Here's a list of questions that you would have to answer to install Digital.ai Release Runner using the xl kube install command.
* Here's a list of questions that you would have to answer to install Digital.ai Release or Runner using the xl kube install command.
PostgreSQL cannot be automatically upgraded during an operator-to-operator or Helm-to-operator upgrade due to incompatible data formats between different PostgreSQL server versions. In such cases, a manual upgrade is necessary. The process involves first backing up the PostgreSQL data, then upgrading to the new PostgreSQL version, and finally restoring the data in the upgraded version.
RabbitMQ during operator2operator upgrade or helm2operator upgrade to version 23.3 of operator will not upgrade automatically to the latest RabbitMQ server version.
This topic illustrates how to set up the persistent volumes on the Release containers.
You use the XL CLI's xl kube command to install or upgrade Digital.ai Deploy or Release, or Release Runner. For more information, see XL Kube Command Reference.
Configuring OIDC is one of the steps in installing or upgrading Digital.ai Deploy or Release using the Operator-based installer.
Configuring OIDC is one of the steps in installing or upgrading Digital.ai Release using the Operator-based installer.
This topic describes how to configure Digital.ai Release on Kubernetes to store reports and task logs on Amazon S3. This setup eliminates the need for persistent volumes, making storage management easier for Kubernetes-based release instances.
* Here's a list of questions that you would have to answer to upgrade Release or Runner using the xl kube upgrade command.
* Here's a list of questions that you would have to answer to upgrade Digital.ai Release Runner using the xl kube upgrade command.
Patch upgrades from 23.3
This topic describes the prerequisites, process and considerations for upgrading to the latest version of Release.
There are certain upgrade considerations if you have Application Pipelines created in Release 24.1 (or earlier) and are now upgrading to Release 24.3. Here's what happens on upgrade of a site from Release 24.1 (or earlier) with Application Pipelines to Release 24.3.