I have created one service called **fleetman-webapp**:

```
apiVersion: v1
kind: Service
metadata:
 name: fleetman-webapp

spec:
 selector:
  app: webapp

 ports:
  - name: http
    port: 80
    nodePort: 30080

 type: NodePort

```

also, a pod named **webapp**:

```
apiVersion: v1
kind: Pod
metadata:
 name: webapp
 labels:
  app: webapp
spec:
 containers:
 - name: webapp
   image: richardchesterwood/k8s-fleetman-webapp-angular:release0

```

I have checked the **minikube ip**:

***192.168.99.102***

But when I type in the browser **192.168.99.102:30080**, the webapp is not reachable:[![enter image description here](https://i.stack.imgur.com/v6GiX.png)](https://i.stack.imgur.com/v6GiX.png)

Please note that I use Ubuntu latest version. I have verified furthermore if proxies and firewalls are active:

**cat /etc/environment**:

```
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"

```

**iptables -L**:

```
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy DROP)
target     prot opt source               destination         
DOCKER-USER  all  --  anywhere             anywhere            
DOCKER-ISOLATION-STAGE-1  all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

Chain DOCKER (1 references)
target     prot opt source               destination         

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target     prot opt source               destination         
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere            
RETURN     all  --  anywhere             anywhere            

Chain DOCKER-ISOLATION-STAGE-2 (1 references)
target     prot opt source               destination         
DROP       all  --  anywhere             anywhere            
RETURN     all  --  anywhere             anywhere            

Chain DOCKER-USER (1 references)
target     prot opt source               destination         
RETURN     all  --  anywhere             anywhere 

```

I have also disabled **ufw** in Ubuntu, but no success, the url **192.168.99.102:30080** .

Would you help me please ? thanks in advance for your answer.
['https://Stackoverflow.com/questions/60710171', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/8384029/']
For this specific (and really great) course about [Kubernetes on Udemy from Richard Chesterwood](https://www.udemy.com/course/kubernetes-microservices/) the following solution should work out of the box on Windows: just start the `minikube` with `hyper-v` driver, then it will automatically map all the ports you are expecting onto your host machine, like detailed explained here by Dawid Kruk. Therefore all you need to start minikube "correctly" is the following command:

```
minikube start --driver=hyperv

```

---

Be careful by specifying exact amount of memory you give to this minikube instance. In my experiences hyper-v is a bit sensitive about how much memory you will give to it, what could result in errors:

```
minikube start --driver=hyperv --memory=8192
...
Not enough memory in the system to start the virtual machine minikube.
Could not initialize memory: Not enough memory resources are available to complete this operation. (0x8007000E).
'minikube' failed to start. (Virtual machine ID D4BC7B61-4E4D-4079-94DE-...)
Not enough memory in the system to start the virtual machine minikube with ram size 8192 megabytes. (Virtual machine ID ...)

```

Therefore just use the unspecific command given above and hyper-v will figure out, how much memory it really needs on it's own.
If you are running minikube in a Windows, then minikube must run as an Administrator command prompt window.