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.
This topic provides information about how to backup Deploy server.
Here are some examples how to backup the content of the Deploy installation on K8s cluster.
From 23.3 version, there are changes how is working answer to the question:
Prerequisites
You can install Deploy in an air-gapped environment that is disconnected from the public internet. This guide provides information for installing and upgrading Deploy in such environments using a Minikube cluster and a custom image registry. While these steps are tailored for Minikube, they can be adapted to other Kubernetes platforms, provided the custom image registry contains all the necessary 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 Deploy 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.
When you upgrade to Deploy 8.0.x from an earlier version, the data stored in Deploy must be converted from the JackRabbit (JCR) format to SQL format.
This topic illustrates how to set up the persistent volumes on the Deploy containers.
This topic describes the Permission service in Digital.ai Deploy.
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 using the Operator-based installer.
Configuring OIDC is one of the steps in installing or upgrading Digital.ai Deploy or Release using the Operator-based installer.
This topic describes the prerequisites, considerations and process for upgrading Deploy from version 10.1 or later to the current version.
* Here's a list of questions that you would have to answer to upgrade Digital.ai Deploy using the xl kube upgrade command.
Patch upgrades from 23.3
This topic provides information on upgrading Deploy. When you upgrade to a new version of Deploy, you must also upgrade your satellite servers to the corresponding version of the satellite distribution ZIP.