tiny

> @mthaddon and @jnsgruk > Perhaps we need to add this to the nginx controller daemonset. > > ```yaml > template: > spec: > hostNetwork: true > ``` I tried...

And if I remove the lines of Liveness and Readiness check configs from daemonset Check one of the running nginx controller pods, I can see the nginx process by `ps...

Thank you @balchua Here is the version information ``` bash-5.1$ /nginx-ingress-controller --version ------------------------------------------------------------------------------- NGINX Ingress controller Release: v0.44.0 Build: f802554ccfadf828f7eb6d3f9a9333686706d613 Repository: https://github.com/kubernetes/ingress-nginx nginx version: nginx/1.19.6 ```

@balchua I think it should look like this with nginx master process and nginx worker process, then port 80 and 443 is listening ``` bash-5.1$ ps -ef PID USER TIME...

> I will have yo reproduce this. Though i didn't look at the processes, but the ingress flow works for me. Thank you, maybe I can try it again tomorow

Finally I disabled the microk8s ingress add-on, and deploy the [nginx-ingress-controller](https://github.com/kubernetes/ingress-nginx) using helm chart, which gives me more configuration flexibility [Here the values.yaml](https://github.com/kubernetes/ingress-nginx/blob/master/charts/ingress-nginx/values.yaml) said that `hostNetwork: true` may be deprecated...