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
Set up a AKS cluster
and check if everything looks fine
kubectl cluster-info
Now try to create a simple pod
kubectl run kubia --image=luksa/kubia --port=8080 --generator=run/v1
now try checking if the pod is created by running kubectl get pods
Pod is running.
now if we try to run kubectl logs it throws and exception after timing out.
Same issue when trying to run kubectl exec -it sh on a pod. but describe works just fine. I am seeing the issue only for the past few days and it was working previously.
The text was updated successfully, but these errors were encountered:
What is the status of the pods running in kube-system? I experienced the same issue while trying to debug #56. Once the kube-svc-redirect pod started working, I was able to get logs again.
Hi @debben I set up a new cluster today and tried running the same steps and I am able to access the logs. If i face the same issue again I would try to check the status of the pods running in kube-system namespace and see if kube-svc-redirect pod is running or having an issue. This is the status of the pods currently and I don't see the issue any more
I had this problem and it turned out that I had a resource that used the subnet dedicated to AKS. you have to check this and if so, remove the resource.
ghost
locked as resolved and limited conversation to collaborators
Aug 12, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Set up a AKS cluster
and check if everything looks fine
kubectl cluster-info
Now try to create a simple pod
kubectl run kubia --image=luksa/kubia --port=8080 --generator=run/v1
now try checking if the pod is created by running kubectl get pods
Pod is running.
now if we try to run kubectl logs it throws and exception after timing out.
Same issue when trying to run kubectl exec -it sh on a pod. but describe works just fine. I am seeing the issue only for the past few days and it was working previously.
The text was updated successfully, but these errors were encountered: