[ ] Review this PR as a team and make sure everyone is aware of all changes
[ ] Reach out to @nickumia if there are any open questions about design choices
[ ] Are the changes breaking?
If yes, check with active members/maintainers/users in #cg-contributors
If no, great job! 🥳
[ ] Are new tests required (and added) for changed resources?
[ ] If fargate is working, do we really want to delete managed node groups?? If we ever need to switch back again, we'll have to revive work in the same way that this PR did to revive fargate 😖
Oooo I think the best way to "consolidate" this is to offer TWO PLANS!! We never really had a use-case for that before this 😲
Background:
In an attempt to leverage k8s for airflow development, the datagov-brokerpak-eks repo needs to be on a supported version of k8s. At the time of writing, there are 130 resources managed by this terraform code. Most of it is documented in our cleanup documentation. These 130 resources are managed through 57 terraform resources and 4 terraform modules (eks, aws_load_balancer_controller, vpc and iam_assumable_role_karpenter). Within these resources, Helm charts are used to create many more intangible resources inside of k8s. Referencing all of the documentation and understanding how to make updates to this is important and requires time and effort.
Many resources were only included because we knew it was dependency, either through direct documentation or trial and error. I'm trying to cover everything before 10/12; however, I suspect that there will be additional work to do. See notes below on the status of current efforts.
Notes:
If there is an EKS cluster provisioned already AND you change tags on the module.eks resource, you MUST delete the current cluster and reprovision from scratch, since the tags interfere with talking to the kubernetes control plane.
Related to
Checklist:
terraform applyrequirement#cg-contributorsBackground: In an attempt to leverage k8s for airflow development, the
datagov-brokerpak-eksrepo needs to be on a supported version of k8s. At the time of writing, there are130 resourcesmanaged by this terraform code. Most of it is documented in our cleanup documentation. These 130 resources are managed through57 terraform resourcesand4 terraform modules(eks,aws_load_balancer_controller,vpcandiam_assumable_role_karpenter). Within these resources, Helm charts are used to create many more intangible resources inside of k8s. Referencing all of the documentation and understanding how to make updates to this is important and requires time and effort.Many resources were only included because we knew it was dependency, either through direct documentation or trial and error. I'm trying to cover everything before 10/12; however, I suspect that there will be additional work to do. See notes below on the status of current efforts.
Notes:
module.eksresource, you MUST delete the current cluster and reprovision from scratch, since the tags interfere with talking to the kubernetes control plane.Misc Notes:
eksmoduleReferences:
autoscaler-provisionertocluster-provisionerdocs