Navigation Menu

Skip to content

0.22.0 Update example/test to use managed Node Group. Fix race conditions when applying the Kubernetes `aws-auth` ConfigMap
Compare
Choose a tag to compare
@aknysh aknysh released this 27 Mar 03:17
0.22.0
79d7bf7
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

what

  • Update example/test to use managed Node Group instead of unmanaged worker nodes
  • Fix race conditions when applying the Kubernetes aws-auth ConfigMap

why

  • Managed Node Groups is an easier way to create an EKS cluster. Tests should use it

  • Ensure ordering of resource creation to eliminate the race conditions when applying the Kubernetes Auth ConfigMap

  • Do not create Node Group before the EKS cluster is created and the aws-auth Kubernetes ConfigMap is applied. Otherwise, EKS will create the ConfigMap first and add the managed node role ARNs to it, and the kubernetes provider will throw an error that the ConfigMap already exists (because it can't update the map, only create it)

  • If we create the ConfigMap first (to add additional roles/users/accounts), EKS will just update it by adding the managed node role ARNs.

Assets 2