X Exiting due to SVC_UNREACHABLE: service not available

[VishalKamaliyaTR]

What Happened?

W1118 12:52:02.659851 29416 root.go:314] Error reading config file at C:\Users\6115721.minikube\config\config.json: open C:\Users\6115721.minikube\config\config.json: The system cannot find the file specified.

Attach the log file

minikube_service_aae5dfb0bb2064c92cabbf0ac41422d89f1fb523_0.log

Operating System

Windows

Driver

Hyper-V

[T-Lakshmi]

@VishalKamaliyaTR,

From the attached logs, below is the error you are encountering.

Exiting due to SVC_UNREACHABLE: service not available: no running pod for service workflow-deployment found.

[T-Lakshmi]

@VishalKamaliyaTR,
It looks you are trying to expose a pod which is actually not available.
could you run the following commands and share the output for debugging:

$ kubectl get services workflow-deployment
$ kubectl describe services workflow-deployment 
$ kubectl get pods -A

[T-Lakshmi]

/kind support

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale