fix pihole liveness probe
This commit is contained in:
@@ -12,8 +12,12 @@ metadata:
|
|||||||
data:
|
data:
|
||||||
unbound.conf: |
|
unbound.conf: |
|
||||||
server:
|
server:
|
||||||
# Listen only on loopback so only the co-located pihole can query it
|
# Listen on all interfaces so the kubelet's liveness/readiness probes
|
||||||
interface: 127.0.0.1
|
# (which connect to the pod IP, not 127.0.0.1) can reach unbound.
|
||||||
|
# No Service exposes port 5335, so it stays cluster-internal; pihole
|
||||||
|
# still forwards to 127.0.0.1#5335 which works because 0.0.0.0 covers
|
||||||
|
# loopback.
|
||||||
|
interface: 0.0.0.0
|
||||||
port: 5335
|
port: 5335
|
||||||
|
|
||||||
# IPv4 only for simplicity
|
# IPv4 only for simplicity
|
||||||
|
|||||||
@@ -1,6 +1,10 @@
|
|||||||
server:
|
server:
|
||||||
# Listen only on loopback so only the co-located pihole can query it
|
# Listen on all interfaces so the kubelet's liveness/readiness probes
|
||||||
interface: 127.0.0.1
|
# (which connect to the pod IP, not 127.0.0.1) can reach unbound.
|
||||||
|
# No Service exposes port 5335, so it stays cluster-internal; pihole
|
||||||
|
# still forwards to 127.0.0.1#5335 which works because 0.0.0.0 covers
|
||||||
|
# loopback.
|
||||||
|
interface: 0.0.0.0
|
||||||
port: 5335
|
port: 5335
|
||||||
|
|
||||||
# IPv4 only for simplicity
|
# IPv4 only for simplicity
|
||||||
|
|||||||
Reference in New Issue
Block a user