Pihole, ingress and subpath, how?! #253

i5Js · 2023-02-16T20:12:10Z

i5Js
Feb 16, 2023

I have the pihole working fine, but I would like to integrate it into a local domain with some services. ex:

domain.k3s.local/longhorn -> longhorn ui
domain.k3s.loca/pihole -> pihole.

But I having issues with the ingress, because, although http://domain.k3s.local/pihole/admin/ works fine, and I get the credential ui, when I type the password, it redirects to http://domain.k3s.local/admin/ and of course it fails. Below you can see my ingress:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    meta.helm.sh/release-name: pihole
    meta.helm.sh/release-namespace: dns-home
    nginx.ingress.kubernetes.io/configuration-snippet: |
      proxy_hide_header X-Frame-Options;
      rewrite ^/pihole/?$ /pihole/admin break;
    nginx.ingress.kubernetes.io/rewrite-target: /$2
  creationTimestamp: "2023-02-16T13:22:59Z"
  generation: 7
  labels:
    app: pihole
    app.kubernetes.io/managed-by: Helm
    chart: pihole-2.11.1
    heritage: Helm
    release: pihole
  name: pihole
  namespace: dns-home
  resourceVersion: "2012116"
  uid: 3c4cefff-4cf1-447c-b3e3-05f568bb8601
spec:
  ingressClassName: nginx
  rules:
  - host: myhome.k3s.local
    http:
      paths:
      - backend:
          service:
            name: pihole-web
            port:
              name: http
        path: /pihole(/|$)(.*)
        pathType: Prefix
status:
  loadBalancer:
    ingress:
    - ip: 192.168.1.122

Any idea?

Thanks, all.

Answered by i5Js

Feb 19, 2023

The way to go

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: pihole
  namespace: dns-home
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$2
    nginx.ingress.kubernetes.io/proxy-buffer-size: "16k"
    nginx.ingress.kubernetes.io/proxy-no-cache: "1"
    nginx.ingress.kubernetes.io/proxy-set-header: Authorization $http_authorization;
    nginx.ingress.kubernetes.io/configuration-snippet: |
      if ($request_uri ~ ^/pihole/?$) {
        return 301 /pihole/admin/;
      }
      if ($request_uri ~ ^/admin/?$) {
        return 301 /pihole/admin/;
      }
  labels:
    app: pihole
spec:
  ingressClassName: nginx
  rules:
  - host: myhome.k3s.local
    http:
  …

View full answer

dwarf-king-hreidmar · 2023-02-19T06:49:01Z

dwarf-king-hreidmar
Feb 19, 2023

Have you tried setting this value:

pihole-kubernetes/charts/pihole/values.yaml

Line 146 in 4025abe

path: /

to /pihole ?

I think then when you login the pihole app will append /pihole to your path before admin

If that doesn't work:
Do you have anything against using subdomains instead? If not this gets a little easier and I have some examples with haproxy if you'd like them.

0 replies

i5Js · 2023-02-19T06:57:21Z

i5Js
Feb 19, 2023
Author

Hey, thanks for your answer. Yes, I did, but it didn't work. With subdomains works fine, I had it in other installation, but my goal is having somthing similar to:
myhome.local/longhorn
myhome.local/pihole
myhome.local/graphana

etc.

3 replies

dwarf-king-hreidmar Feb 19, 2023

Do you still need rewrite rules if you change that path? Have you checked if the default path of the app actually changes?

dwarf-king-hreidmar Feb 19, 2023

I would expect this to work like: you set up base path in nginx that goes to your upstream server (in this case correctly labled pods).

Once you reach your app if it properly passes path it would always send $URL/$BASEPATH/$PATH back to your browser.. no nginx rewrite needed but maybe I'm mistaken

dwarf-king-hreidmar Feb 19, 2023

Now that I'm looking at this closer this sets the path in ingress not in the app. If we could do that was supported it would be cleaner .. let me look around a bit

i5Js · 2023-02-19T07:06:16Z

i5Js
Feb 19, 2023
Author

This is my actual ingress... still redirecting to /admin/ if it helps:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: pihole
  namespace: dns-home
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$2
    nginx.ingress.kubernetes.io/proxy-buffer-size: "16k"
    nginx.ingress.kubernetes.io/proxy-no-cache: "1"
    nginx.ingress.kubernetes.io/proxy-set-header: Authorization $http_authorization;
    nginx.ingress.kubernetes.io/configuration-snippet: |
      if ($request_uri ~ ^/pihole/?$) {
        return 301 /pihole/admin;
      }
  labels:
    app: pihole
spec:
  ingressClassName: nginx
  rules:
  - host: myhome.k3s.local
    http:
      paths:
      - path: /pihole(/|$)(.*)
        pathType: Prefix
        backend:
          service:
            name: pihole-web 
            port:
              name: http
      - path: /pihole
        pathType: Prefix
        backend:
          service:
            name: pihole-web 
            port:
              name: http

11 replies

i5Js Feb 19, 2023
Author

Which means

The default backend is a service which handles all URL paths and hosts the Ingress-NGINX controller doesn't understand (i.e., all the requests that are not mapped with an Ingress).

https://kubernetes.github.io/ingress-nginx/user-guide/default-backend/

dwarf-king-hreidmar Feb 19, 2023

Are you willing to manipulate the html folder and move everything to /pihole/admin and then grep for everywhere you need to change it? This seems like the worst of the solutions but I bet it would work if you really need to change the PATH instead of the subdomain. I think its crazy pihole its self doesn't have a way to set the basepath

some poor souls doing this: https://raspberrypi.stackexchange.com/questions/52090/how-do-i-change-pi-holes-url-path

i5Js Feb 19, 2023
Author

I think I get it. With this ingress, everything works now!!

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: pihole
  namespace: dns-home
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$2
    nginx.ingress.kubernetes.io/proxy-buffer-size: "16k"
    nginx.ingress.kubernetes.io/proxy-no-cache: "1"
    nginx.ingress.kubernetes.io/proxy-set-header: Authorization $http_authorization;
    nginx.ingress.kubernetes.io/configuration-snippet: |
      if ($request_uri ~ ^/pihole/?$) {
        return 301 /pihole/admin/;
      }
      if ($request_uri ~ ^/admin/?$) {
        return 301 /pihole/admin/;
      }
  labels:
    app: pihole
spec:
  ingressClassName: nginx
  rules:
  - host: myhome.k3s.local
    http:
      paths:
      - path: /pihole(/|$)(.*)
        pathType: Prefix
        backend:
          service:
            name: pihole-web 
            port:
              name: http
      - path: /pihole
        pathType: Prefix
        backend:
          service:
            name: pihole-web 
            port:
              name: http
      - path: /admin/
        pathType: Prefix
        backend:
          service:
            name: pihole-web 
            port:
              name: http

That was the key:

      if ($request_uri ~ ^/admin/?$) {
        return 301 /pihole/admin/;
      }

Basically, if you get /admin/ redirect to /pihole/admin. and Booom! worked.

dwarf-king-hreidmar Feb 19, 2023

Really nice catch. I totally missed that!

i5Js Feb 19, 2023
Author

Time to move theses settings to the values.yaml :)

i5Js · 2023-02-19T07:35:45Z

i5Js
Feb 19, 2023
Author

The way to go

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: pihole
  namespace: dns-home
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$2
    nginx.ingress.kubernetes.io/proxy-buffer-size: "16k"
    nginx.ingress.kubernetes.io/proxy-no-cache: "1"
    nginx.ingress.kubernetes.io/proxy-set-header: Authorization $http_authorization;
    nginx.ingress.kubernetes.io/configuration-snippet: |
      if ($request_uri ~ ^/pihole/?$) {
        return 301 /pihole/admin/;
      }
      if ($request_uri ~ ^/admin/?$) {
        return 301 /pihole/admin/;
      }
  labels:
    app: pihole
spec:
  ingressClassName: nginx
  rules:
  - host: myhome.k3s.local
    http:
      paths:
      - path: /pihole(/|$)(.*)
        pathType: Prefix
        backend:
          service:
            name: pihole-web 
            port:
              name: http
      - path: /pihole
        pathType: Prefix
        backend:
          service:
            name: pihole-web 
            port:
              name: http
      - path: /admin/
        pathType: Prefix
        backend:
          service:
            name: pihole-web 
            port:
              name: http

I hope it helps for someone else

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Pihole, ingress and subpath, how?! #253

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 4 comments 14 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Pihole, ingress and subpath, how?! #253

i5Js Feb 16, 2023

Replies: 4 comments · 14 replies

dwarf-king-hreidmar Feb 19, 2023

i5Js Feb 19, 2023 Author

dwarf-king-hreidmar Feb 19, 2023

dwarf-king-hreidmar Feb 19, 2023

dwarf-king-hreidmar Feb 19, 2023

i5Js Feb 19, 2023 Author

i5Js Feb 19, 2023 Author

dwarf-king-hreidmar Feb 19, 2023

i5Js Feb 19, 2023 Author

dwarf-king-hreidmar Feb 19, 2023

i5Js Feb 19, 2023 Author

i5Js Feb 19, 2023 Author

i5Js
Feb 16, 2023

Replies: 4 comments 14 replies

dwarf-king-hreidmar
Feb 19, 2023

i5Js
Feb 19, 2023
Author

i5Js
Feb 19, 2023
Author

i5Js Feb 19, 2023
Author

i5Js Feb 19, 2023
Author

i5Js Feb 19, 2023
Author

i5Js
Feb 19, 2023
Author