Preparing to install

Setup for the necessary tools to install the operator.

Pre-requirements

Get familiarized with the architecture reading this section.

A valid Disaster Recovery Operator license key and registry access key should already be assigned.

Supported platforms

Astronetes Disaster Recovery Operator is vendor agnostic meaning that any Kubernetes distribution such as Google Kubernetes Engine, Azure Kubernetes Service, OpenShift or self-managed bare metal installations can run it.

This is the certified compatibility matrix:

Platform	Min Version	Max Version
AKS	1.24	1.29
EKS	1.24	1.28
GKE	1.24	1.28
OpenShift Container Platform	4.11	4.14

Software

Official kubernetes.io client CLI kubectl.

Networking

Allow traffic to the Image Registry quay.io/astrokube using the mechanism provided by the chosen distribution.
In a 3-clusters architecture, the management cluster needs to have communication with both the destination and source cluster. Note that it is not necessary to also allow connections between the target clusters. Due to the lack of a centralised management cluster, in a 2-clusters architecture communication between destination and source should be enabled.

Cluster configuration

Cluster admin permission in management, destination and source clusters. In a 2-clusters architecture it is only required to have admin permissions in the destination and source clusters as the operator activities will be delegated to the former.
The Secret provided by AstroKube to access the Image Registry.
The Secret provided by AstroKube with the license key.

Software

OpenShift client CLI.

Networking

Add quay.io/astrokube to the allowed registries in the Image configuration.
In a 3-clusters architecture, the management cluster needs to have communication with both the destination and source cluster. Note that it is not necessary to also allow connections between the target clusters. Due to the lack of a centralised management cluster, in a 2-clusters architecture communication between destination and source should be enabled.

apiVersion: config.openshift.io/v1
kind: Image
metadata:
    ...
spec:
  registrySources: 
    allowedRegistries: 
    ...
    - quay.io/astrokube

Cluster configuration

Cluster admin permission in management, destination and source clusters. In a 2-clusters architecture it is only required to have admin permissions in the destination and source clusters as the operator activities will be delegated to the former.
The Secret provided by AstroKube to access the Image Registry.
The Secret provided by AstroKube with the license key.