Skip to main content
Version: v1.1

1.1.0

When the Luna option reuseBinSelectNodes is set true (default), Luna-managed pods with matching node selection characteristics can reuse bin-select nodes and node pools, and nodes can be allocated for multiple bin-select pods with single multi-node scale-up operations. To determine if bin-select pods have matching node selection characteristics, Luna compares a hash of the pods' K8s representation with a set of non-node-selection-related fields cleared.

In version 1.1.0 of Luna, the K8s libraries are updated, impacting the computed reuse hash value, so existing bin-select nodes and node pools will not be reused after upgrade. If you would like existing bin-select pods to share node pools created for matching pods after Luna upgrade to 1.1.0, please restart the old bin-selected pods.

Note that we have updated our hash computation for node reuse to only apply to fields that explicitly impact Luna's configuration of nodes and node pools for bin-select to avoid a similar impact for Luna K8s library upgrades in the future.

0.7.0

EKS​

Luna can now query image families in EKS from the System Manager parameter Store. As a result Luna manager 0.6.7+ requires additional IAM permissions ssm:GetParameter to query the SSM database to get the image ID.

To upgrade to 0.7.0 from a previous version you can either:

  1. Uninstall Luna and reinstall it with the deploy.sh script
  2. Edit the IAM policy attached to the Luna manager service account

For option #2, the IAM policy will be named ${CLUSTER_NAME}-${NAMESPACE}-LunaAssumeRoleWithWebIdentity.

Here’s how to change the policy for Luna 0.6.7:

                 "ec2:DescribeKeyPairs",
                 "ec2:DescribeSecurityGroups",
                 "iam:PassRole",
-                "iam:GetInstanceProfile"
+                "iam:GetInstanceProfile",
+                "ssm:GetParameter"
             ],
             "Resource": "*"
         },