AWS Elastic Kubernetes Service (EKS) is a managed infrastructure for container orchestration. In our organisation it is secured by Okta/MFA. The daily mood I am motivated. My goal is to move simple assets from my local cluster (deployment source) to our remote/shared one (deployment target). For this I need to require access to a GitHub enterprise hosting our configuration repository, and an AWS Elastic Kubernetes Service (EKS) for running development workloads. Note: We also have cluster instances running on AWS virtual machines (EC2) and containers (ECS) which we manage using Kubespray , as well as cluster instances in Azure Kubernetes Service (AKS). As far as I know, we do not use KOPS , another popular tool for installing and launching Kubernetes clusters in different cloud infrastructures. Access authorization GitHub Enterprise was pretty straight forward. I already had a personal account which just needed to be mapped with our organisation. Then ...
Learnings & thoughts collected on-the-job