You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 19, 2024. It is now read-only.
By default, when you deploy with a click of a button, it doesn't set the cluster_name variable at all. And now I am wondering how is this expected to work?
Also note: The lambda function itself doesn't handle errors well and makes everything look like it has worked
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Code parses the cluster name from ec2 instance tag according to this line - https://github.com/awslabs/amazon-eks-serverless-drainer/blob/master/main.sh#L37-L38
But when setting kubeconfig, it's using
cluster_name
variable which is different from the parsed cluster name (input_cluster_name
) - https://github.com/awslabs/amazon-eks-serverless-drainer/blob/master/main.sh#L41By default, when you deploy with a click of a button, it doesn't set the
cluster_name
variable at all. And now I am wondering how is this expected to work?Also note: The lambda function itself doesn't handle errors well and makes everything look like it has worked
The text was updated successfully, but these errors were encountered: