2.1 Prerequisites and Considerations

Create a cluster setup and identify the Master and Worker nodes.

Set up a Calico network for communication between pods across Kubernetes nodes. For information about setting up a Calico network, see Calico networking for Kubernetes.

DNS resolution happens between all the pods in your cluster.

To ensure that the communication between pods happen through Fully Qualified Domain Name (FQDN), ensure that you update the FQDN entries of all the master and worker nodes on all the nodes where pods will be deployed.

Based on the Identity Manager components you want to deploy in your environment, ensure that the appropriate container resources like memory, CPU, and so on, are available in all the nodes in your environment.

For more information about assigning the memory resource, see Kubernetes documentation.

For more information about assigning the CPU resource, see Kubernetes documentation.

Ensure that the appropriate volumes are available in each of the nodes.

Persistent Volume Claim is used for requesting storage space, through the YAML files, for each pods deployed on your nodes.

Ensure that certificates are available before deploying the pods. For information about generating the certificates, see Generating Certificates With Identity Vault Certificate Authority.

(Conditional) If you want to establish a communication between an on-premise environment and Kubernetes cluster present in a different environment, set up a Virtual Private Networking (VPN) between Kubernetes cluster and on-premise for secure communication.

Ensure NGINX service is set up to expose HTTPS outside the Kubernetes cluster environment. For information on setting up the NGINX service in a Kubernetes environment, see Kubernetes documentation.

Some containers are dependent on others. The following table provides details on those containers that are dependent on other containers.