netmaker-helm
netmaker-helm copied to clipboard
Does not automatically ingress the UI, API etc. with working NGINX
I know this is an internal IP - I am simply testing at current. This ingress only shows a blank NGINX page - cert-manager is working fine... How do i troubleshoot ? It should into create as i have all pre-reqs any needed ingress
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default kubernetes ClusterIP 10.254.0.1 <none> 443/TCP 4d4h
default netmaker-1655235886-grpc ClusterIP 10.254.228.148 <none> 443/TCP 2d6h
default netmaker-1655235886-postgresql-ha-pgpool ClusterIP 10.254.113.245 <none> 5432/TCP 2d6h
default netmaker-1655235886-postgresql-ha-postgresql ClusterIP 10.254.0.236 <none> 5432/TCP 2d6h
default netmaker-1655235886-postgresql-ha-postgresql-headless ClusterIP None <none> 5432/TCP 2d6h
default netmaker-1655235886-rest ClusterIP 10.254.231.46 <none> 8081/TCP 2d6h
default netmaker-1655235886-ui ClusterIP 10.254.189.228 <none> 80/TCP 2d6h
default netmaker-1655235886-wireguard NodePort 10.254.101.191 <none> 31821:31821/UDP,31822:31822/UDP,31823:31823/UDP,31824:31824/UDP,31825:31825/UDP,31826:31826/UDP,31827:31827/UDP,31828:31828/UDP,31829:31829/UDP,31830:31830/UDP 2d6h
ingress-nginx ingress-nginx-controller LoadBalancer 10.254.80.250 192.168.5.76 80:30624/TCP,443:31316/TCP 3d19h
ingress-nginx ingress-nginx-controller-admission ClusterIP 10.254.93.22 <none> 443/TCP 3d19h
kube-system dashboard-metrics-scraper ClusterIP 10.254.250.211 <none> 8000/TCP 4d4h
kube-system kube-dns ClusterIP 10.254.0.10 <none> 53/UDP,53/TCP,9153/TCP 4d4h
kube-system kubernetes-dashboard ClusterIP 10.254.179.22 <none> 443/TCP 4d4h
kube-system magnum-metrics-server ClusterIP 10.254.200.48 <none> 443/TCP
Is this project actively maintained?
Hi, the project has just been updated and now works for the latest version. I am guessing your issue is with the certificate class name. By default it uses "letsencrypt-prod". If your certificate class name is different you will have to change that. Typically to debug I will run "kubectl describe certificate (certificate name)". It will usually show a pending request, and you can go down the chain of certificate request to other objects to find where it's stuck.