This document describes the Dex project implementation designed to deploy this service with airshipctl phase run command. This deployment relies on Helm toolset, i.e., Helm operator and Helm (ChartMuseum) repository. Throughout this document the term Target Cluster will be used referring to a cluster that was deployed using "airshipctl phase run" command, starting with an Ephemeral cluster, e.g., Kind cluster. Dex Deployment The diagram below illustrates the desired architecture of the Dex Deployment object (DEX POD). Three containers are created within the Dex POD: NGINX - This container plays the role of reverse-proxy redirecting https traffic to the Dex Authenticator container (/ui) and Dex application container (/dex). Dex Authenticator - This container stores the webapp for authenticating an user. Dex - This container run the Dex application, which integrates with an external Identity Provider (IdP), e.g. LDAP.