ikarlashov

@jrhouston no problem :) I don't think there's such env variable. I execed to the gitlab-runner pod and there're the following k8s-related vars: ``` KUBERNETES_PORT_443_TCP_PORT=443 KUBERNETES_PORT=tcp://172.20.0.1:443 KUBERNETES_SERVICE_PORT=443 FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY=false KUBERNETES_SERVICE_HOST=172.20.0.1 KUBERNETES_PORT_443_TCP_PROTO=tcp...

We faced this issue as well. It's related to the lack of IAM permissions for either cluster or node_group(s). Also make sure that you have correct KMS key ARN specified...

Ok, I found the issue. Spent a few hours, ofc :( What can I say: handling errors during VM startup could be done better on lima side (sorry, I can't...