Open brian-bk opened 3 weeks ago
Hmmm...I tried this with my own EKS cluster, and was not able to repro.
I went through all the changes between 0.33.8 and 0.33.9 and didn't see any changes that would affect how tilt computes cluster status.
can you post the output of:
kubectl get -v=6 --raw /version
?
Sure thing
$ kubectl get -v=6 --raw /version
I0607 11:02:35.245274 24199 loader.go:374] Config loaded from file: /Users/briankleszyk/.kube/config
I0607 11:02:35.953061 24199 round_trippers.go:553] GET https://<redacted>.gr7.us-east-1.eks.amazonaws.com/version 200 OK in 706 milliseconds
{
"major": "1",
"minor": "27+",
"gitVersion": "v1.27.13-eks-3af4770",
"gitCommit": "4873544ec1ec7d3713084677caa6cf51f3b1ca6f",
"gitTreeState": "clean",
"buildDate": "2024-04-30T03:31:44Z",
"goVersion": "go1.21.9",
"compiler": "gc",
"platform": "linux/amd64"
}
🤷 don't know if relevant or not but I (and most of our engineers) are using arm64, with a amd64 cluster.
Expected Behavior
Tilt should be able to connect to the cluster on
tilt up
etc.Current Behavior
Tilt is unable to connect to the cluster directly. We still see tilt managing
local_resources
and our Tiltfile executes somekubectl
commands manually vialocal
orlocal_resource
, but the managed k8s resources behind ahelm_resource
do not work. In addition after the Tiltfile processing finishes there's a noted failure on the(Tiltfile)
resource.We have tested and in 0.33.8 this works without such issue, and I tested with 0.33.15 and the issue since 0.33.9 still persists.
Steps to Reproduce
tilt up
kubectl
commands from inside alocal
orlocal_resource
resources workContext
tilt doctor
OutputAbout Your Use Case
This has been happening since 0.33.9 and I forgot to report it right away. This still happens on 0.33.15. For now we've actually added a check in our Tiltfile to force people on to <=0.33.8, until this can be resolved. Maybe it's specific to Amazon EKS's authentication, but I'm not sure.