Section 2: Shared Resources Deployment Activities
Prep steps can be deployed once per group if EKS deployment and integration is not the main focus. For individuals or those practicing cluster setup and integration, these can be done by each participant as well
Dependencies: All labs depend on section 2 because it sets up the cluster and GitLab integration.
Outcomes: Deploy EKS with official AWS IaC in a cost-efficient format for training (performed by instructor for instructor-led)
Visual Overview of GitLab Agent Group Level Cluster Integration
Click Here To Expand a Visual Overview of GitLab Agent Group Level Cluster Integration
Key Aspects:
- While the cluster integration project lives within the group, the configuration file can point to it’s parent group.
- Specific GitLab variables are set at the group level and inherit by all downbound groups.
- KUBE_CONTEXT and KUBE_INGRESS_BASE_DOMAIN are shared with all projects to ensure they work appropriately in the cluster.
- The KUBE_NAMESPACE variable uses project variables that are unique to ensure all projects go into the cluster uniquely
- KUBE_NAMESPACE is overridden in GitOps projects to include the environment.
- REG_READ_TOKEN - Only Read Access, Only to the Container Registry is given. In labs this is a Deployment Token. In production it should use a Group Access Token to give read permissions to all App Build Project container registries to all related Environment Deployment Projects.
Visual Overview of Agent Registration Process
Click Here To Expand a Visual Overview of The Agent Registration Process
