mirror of
https://github.com/mulgadc/spinifex.git
synced 2026-11-06 19:01:10 +00:00
Josh Siviour
8e3ccf45c4
* test(eks): specify the AWS-style cluster security group layout * feat(eks): give clusters one AWS-style cluster security group Create the eks-cluster-sg-<name>-<id> SG in the customer VPC with the EKS tags and a self rule, report it as clusterSecurityGroupId, launch workers with it (or the launch template's SGs), and attach it to the private-endpoint ENI. New clusters no longer get customer-VPC control-plane and nodegroup SGs; clusters created before keep theirs, and delete finds the new SG by tag. * fix(eks): own the cluster SG by its recorded id and scope the delete sweep Workers and teardown use the SG id recorded on the cluster; a create retry only adopts an SG carrying tags the service alone can set. DeleteClusterSGs now revokes every rule only on cluster-owned SGs and, on any other SG in the VPC, only the rules that reference one. * docs(eks): use the cluster security group in workbooks and e2e Workbooks read vpc_config[0].cluster_security_group_id and drop the hand NodePort rules. E2E covers an internet-facing instance-target ALB with no hand rule, exec and logs, and a bystander security group surviving DeleteCluster. * docs(eks): drop stale node-group SG sentence