AWS Auth Second Attempt
What does this MR do?
Attempt number 2 of https://gitlab.com/gitlab-org/quality/gitlab-environment-toolkit/-/merge_requests/302. In the first attempt, the change broke non-hybrid environments because it was attempting to connect to the non-existent EKS cluster (as spotted by @cat)
Adds support for AWS Authentication for EKS clusters, as per https://gitlab.com/gitlab-org/quality/gitlab-environment-toolkit/-/issues/216
Related issues
- Closes https://gitlab.com/gitlab-org/quality/gitlab-environment-toolkit/-/issues/216
- https://gitlab.com/gitlab-org/quality/gitlab-environment-toolkit/-/issues/207
- https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/issues/135
Related issues
Author's checklist
When ready for review, the Author applies the workflowready for review label:
- Merge request:
-
Corresponding Issue raised and reviewed by the GET maintainers team. -
Merge Request Title and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline
-
- Code:
-
Check the area changed works as expected. Consider testing it in different environment sizes (1k,3k,10k,etc.). -
Documentation created/updated in the same MR. -
If this MR adds an optional configuration - check that all permutations continue to work. -
For Terraform changes: setup a previous version environment, then run a terraform planwith your new changes and ensure nothing will be destroyed. If anything will be destroyed and this can't be avoided please add a comment to the current MR.
-
-
Create any follow-up issue(s) to support the new feature across other supported cloud providers or advanced configurations. Create 1 issue for each provider/configuration. Contact the Quality Enablement team if unsure.
Edited by Grant Young