Deploy to Amazon EKS Using Digital.ai Deploy and Release
This how-to demonstrates how you can leverage the Digital.ai Deploy and Release applications' capabilities and deploy your application to the Amazon EKS test and prod namespaces.
This how-to demonstrates how you can leverage the Digital.ai Deploy and Release applications' capabilities and deploy your application to the Amazon EKS test and prod namespaces.
The Kubernetes plugin supports discovery of k8s.Master and k8s.Namespace CIs from a Kubeconfig file. To discover,
You can install Deploy in an air-gapped environment disconnected from the public internet. This topic provides information about installing and upgrading Deploy 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.
Prerequisites
Prerequisites
Prerequisites
Prerequisites
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 or Release using the xl kube install command.
This topic covers the Deploy Kubernetes (K8s) plugin, which supports creating and managing Kubernetes resources such as Namespaces, Pods, Deployments, ConfigMaps, Secrets, and more, using various authentication methods.
Here's what it takes to manage Digital.ai Deploy plugins on a Deploy cluster that was created using the Operator-based installer:
You use the XL CLI's xl kube command to install or upgrade Digital.ai Deploy or Release or Remote 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.
* Here's a list of questions that you would have to answer to install Digital.ai Deploy or Release using the xl kube upgrade command.
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 daideploy_cr.yaml file.