Windows用户Minikube部署REST API后的访问问题咨询

Hey there! Let's work through this issue step by step since you're new to Kubernetes and Minikube on Windows. I've been in your shoes before, so let's break down the common culprits here:

1. Verify Minikube Network Reachability #

First, let's make sure your Windows machine can actually reach the Minikube node:

• Open Command Prompt or PowerShell and run:

  ping 192.168.0.29
  

  If you get consistent packet loss, this points to a network driver issue. Minikube on Windows typically uses Docker Desktop or Hyper-V as its driver—confirm the driver is healthy with:

  minikube status
  

  Also double-check the Minikube node IP matches what you're using by running:

  minikube ip
  

2. Validate Your Service Configuration #

Next, let's ensure your Service is properly routing traffic to your Pod:

• Fetch the full Service YAML to inspect key settings:

  kubectl get service <your-service-name> -o yaml
  

  Verify these critical fields:
  • spec.type should be NodePort (since you're using a port like 32246)
  • spec.ports[0].targetPort must match the 5000 port your REST API exposes inside the container
  • spec.selector should exactly match the labels defined in your Deployment/Pod (this is how the Service finds your Pods)
• You can also check for runtime issues with:

  kubectl describe service <your-service-name>
  

  Look at the Endpoints section—if it's empty, your Service isn't matching any Pods.

3. Check Pod and Container Health #

If the Service looks good, confirm your API is running properly inside the Pod:

• First, check if your Pod is in a healthy Running state:

  kubectl get pods
  

  If you see CrashLoopBackOff or Error, retrieve the container logs to debug why the API isn't starting:

  kubectl logs <your-pod-name>
  

• If the Pod is running, test the API directly inside the container to rule out network routing issues:

  kubectl exec -it <your-pod-name> -- curl http://localhost:5000/Hello/test-string
  

  If this returns a successful response, your API works internally—so the problem is external access.

4. Rule Out Windows Firewall/Security Software #

Windows Defender Firewall or third-party antivirus tools often block incoming traffic to Minikube's NodePorts:

• Temporarily disable Windows Defender Firewall (only for testing purposes) and try accessing the URL again. If it works, you'll need to create an inbound rule allowing traffic to port 32246.
• If you have third-party security software, temporarily disable it to see if it's interfering.

5. Use Minikube's Built-in Service Access Command #

Minikube has a handy command that handles network forwarding automatically, which can bypass manual IP/port issues:

minikube service <your-service-name>

This command will either open your browser directly to the correct URL or print a working access address—this is especially reliable if you're using Docker Desktop as your Minikube driver.

Start with these steps, and we can narrow down exactly where the issue is!

内容的提问来源于stack exchange，提问作者sacha barber