57 docs tagged with "kubernetes"

Advanced configuration options for Digital.ai Release on Kubernetes, including custom site configurations, persistent volumes, external databases, and secret references.

Learn how to manage application images in air-gapped environments. Following are the five different options you can use to ensure your application images are available in air-gapped environments.

Steps to perform an automatic in-place PostgreSQL major version upgrade with the CloudNativePG operator, and when to fall back to the manual upgrade process.

This document provides procedures for backing up the Digital.ai Release installation on a Kubernetes (K8s) cluster. Follow these steps to ensure your data and configuration are protected before performing upgrades or maintenance.

Configure basic settings for Digital.ai Release on Kubernetes, including custom resource parameters, licensing, node selection, and resource sizing.

Important changes to Bitnami container images that impact Digital.ai Release Kubernetes Operator installations and upgrades.

Install or upgrade Digital.ai Release on cloud Kubernetes platforms including AWS EKS, Google GKE, Azure AKS, and on-premise clusters.

Learn how to enable and configure Horizontal Pod Autoscaler (HPA) to automatically scale Release pods based on resource utilization

This topic illustrates how to configure the settings required to install Release with HTTP2 backend enabled on a Kubernetes cluster.

Select the JDK version for an operator-based Release installation by setting the container image tag in the custom resource.

This guide explains how to configure the DNS Time-to-Live (TTL) settings for the Release Java Virtual Machine (JVM) in a Kubernetes environment. Proper TTL configuration is crucial for managing how long DNS resolutions are cached, which can affect system performance and network behavior.

How to expose deployments that already run on a Flux CD server in the Release Live Deployments dashboard.

How to expose deployments that already run on an Argo CD server in the Release Live Deployments dashboard.

Before You Begin

This guide explains how custom resource keys are migrated during the Digital.ai Release operator upgrade process. Understanding this process is crucial for maintaining your configuration when upgrading to newer versions of the operator.

Here's a video walk-through.

When running Digital.ai Release with HTTPS enabled in Kubernetes, you may need to disable the Server Name Indication (SNI) check in certain scenarios. This guide explains how to safely disable the SNI check using Kubernetes commands.

This guide explains how to manage file system operations in Digital.ai Release when using Operator-based installation. By default, containers run with read-only file systems for enhanced security. Learn how to configure various storage options including temporary storage, persistent volumes, and custom mounts to meet your application's needs while maintaining security best practices.

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.

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 Release installation.

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 Release installation.

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 Release installation.

Here is a basic setup for the AWS Openshift cluster, use it as a guideline to create K8s cluster to have minimal K8s environment for Digital.ai Release installation.

Use these instructions to install Digital.ai Release on a minikube multi-node cluster for testing or illustration purposes. Do not use these instructions to set up a production environment.

Reference for all installation options and prompts when installing Digital.ai Release on Kubernetes using the xl kube install command.

* Here's a list of questions that you would have to answer to install Digital.ai Release Runner using the xl kube install command.

Reference for the questions and options presented during Digital.ai Release installation with xl kube install.

How to install Digital.ai Release on Red Hat OpenShift using the OpenShift Certified Operator.

The Release Kubernetes plugin allows user to connect to different K8s clusters using Kubectl and perform operations. The plugin also allows the user to lookup Kube Contexts from a config file that the user provides and connect to a specific cluster from a list of configs.

The Kubernetes container plugin offers a range of functionalities to enhance Kubernetes cluster management, deployment, and operations.

The Kubernetes Plugin (Jython-based) integrates Digital.ai Release with Kubernetes to automate resource management, execute commands, and monitor workloads as part of your release workflows.

Diagnose and resolve issues with Digital.ai Release and Release Runner on Kubernetes.

This guide explains how to manage Digital.ai Release plugins in offline mode when working with a Release cluster created using the Operator-based installer. You'll learn multiple approaches to manage plugins when the Release UI is unavailable or not functioning properly.

This guide covers the manual steps required to upgrade PostgreSQL across a major version when using the CloudNativePG (CNPG) operator-based PostgreSQL installation, specifically when PostgreSQL is managed through the experimental postgresql-operator and postgresql-cluster rather than through the Release CR's built-in spec.postgresql keys. Use this manual process only if the automatic upgrade fails or your cluster doesn't meet its prerequisites.

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.

This guide covers the manual steps required to migrate from the Bitnami chart-managed PostgreSQL installation (the default up to and including operator 25.1 releases) to the CloudNativePG (CNPG) operator-managed equivalent introduced in operator 25.3 releases.

How to move off the removed nginx, haproxy, and ingress-nginx-controller components and configure an external ingress controller when upgrading to Release VAR::version_short or later.

This topic illustrates how to set up the persistent volumes on the Release containers.

Prerequisites and planning information for installing or upgrading Digital.ai Release on Kubernetes.

From 23.3 plugin management is possible with XL CLI utility. For more information, see Plugin Manager CLI.

Before You Begin

This topic illustrates how to use the diagnostic mode in Release.

Kubernetes provides flexible mechanisms to control pod scheduling across your cluster nodes. This guide explores three powerful options for scheduling pods to specific nodes: node selectors, node affinity, and tolerations. Each approach offers different levels of control and complexity to help you optimize your workload placement.

Configure security settings for Digital.ai Release on Kubernetes, including OIDC authentication, TLS/SSL, truststore setup, and HTTP2.

Configuring OIDC is one of the steps in installing or upgrading Digital.ai Release using the Operator-based installer.

This article explains how to set up a custom image registry for installing or upgrading Release. A custom image registry can be either public (not password-protected) or private (password-protected).

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.

Configure system-level settings for Digital.ai Release on Kubernetes, including JVM arguments, logging, autoscaling, and JDBC drivers.

The Tekton Container Plugin for Digital.ai Release lets you trigger and monitor Tekton pipelines from a release flow. Tekton is a Kubernetes-native CI/CD engine that defines workflows using custom resources such as Pipeline, Task, and PipelineRun.

You must use the custom resource definition file (CR file) in case you want to change the Digital.ai Release's license on sites installed using the Operator-based installer.

Upgrade Digital.ai Release and Release Runner on Kubernetes, and migrate configurations during upgrades.

Reference for the questions and options presented when upgrading Digital.ai Release with xl kube upgrade.

* 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

If you plan to use an existing database—one that is not created by default by the Operator-based installer—you must configure the relevant database parameters in the dairelease_cr.yaml file.

This topic illustrates how to use an external database instead of the one that is provided with the operator itself.

This topic illustrates how to replace the CR values that are in clear-text format in the CR with the secret references.