Currently when you run boatswain check-ami on an AWS account it checks ALL the autoscaling groups in that AWS account if they are the most up to date ami. This causes all kind of issues:
it checks autoscaling groups that are not even used by EKS
if you have an AWS cluster with two clusters with different versions, like 1.20 and 1.19 every check-ami run will complain that the autoscaling groups of the other cluster are wrong.
there is a way to filter ASGs: kubernetes.io/cluster/[clustername]
So we could make sure to only check the ASGs actually used by the current cluster
Alternatives
Noting really, creating a new AWS Account for each EKS cluster, but that's quite a hard workaround
Context
Currently when you run
boatswain check-ami
on an AWS account it checks ALL the autoscaling groups in that AWS account if they are the most up to date ami. This causes all kind of issues:check-ami
run will complain that the autoscaling groups of the other cluster are wrong.there is a way to filter ASGs:
kubernetes.io/cluster/[clustername]
So we could make sure to only check the ASGs actually used by the current clusterAlternatives
Noting really, creating a new AWS Account for each EKS cluster, but that's quite a hard workaround