This message was deleted.
# epinio
a
This message was deleted.
b
hm, that's a very limited scenario that I don't think we have ever tested or thought about.. it could theoretically be possible but it's a new feature, and probably not so easy to implement, because of some default assumptions
k
I got it! thank you for answering.
@broad-dream-81849 I continue on the mission to reduce epinio's scope on restricted cluster. Now i'm stuck on this error,
Copy code
❌  error creating handler: couldn't check kubeconfig; ensure kubeconfig is correct to continue: invalid kube config: Get "<https://10.100.0.1:443/version>": dial tcp 10.100.0.1:443: i/o timeout
Do you have any idea about where this connection is being blocked/dropped, i'm running on eks.
I got this error on epinio-server pod.
ps: those ips, doesn't exist in my network.
I've found it, the issue was related to eks.
🎉 1