46 lines
1.5 KiB
YAML
46 lines
1.5 KiB
YAML
# Here we will setup the values needed to setup BunkerWeb behind an existing ingress controller
|
|
# Traffic flow with BW: LB => existing Ingress Controller => BunkerWeb => Service
|
|
# Traffic flow without BW: LB => existing Ingress Controller => Service
|
|
|
|
# Global settings
|
|
settings:
|
|
misc:
|
|
# Replace with your DNS resolver
|
|
# to get it: kubectl exec in a random pod then cat /etc/resolv.conf
|
|
# if you have an IP as nameserver then do a reverse DNS lookup: nslookup <IP>
|
|
# most of the time it's coredns.kube-system.svc.cluster.local or kube-dns.kube-system.svc.cluster.local
|
|
# dnsResolvers: "kube-dns.kube-system.svc.cluster.local"
|
|
dnsResolvers: "default.svc.cluster.local"
|
|
kubernetes:
|
|
# We only consider Ingress resources with ingressClass bunkerweb to avoid conflicts with existing ingress controller
|
|
ingressClass: "bunkerweb"
|
|
# Optional: you can choose namespace(s) where BunkerWeb will listen for Ingress/ConfigMap changes
|
|
# Default (blank value) is all namespaces
|
|
namespaces: ""
|
|
|
|
# Override the bunkerweb-external service type to ClusterIP
|
|
# Since we don't need to expose it to the outside world
|
|
# We will use the existing ingress controller to route traffic to BunkerWeb
|
|
service:
|
|
type: ClusterIP
|
|
|
|
# BunkerWeb settings
|
|
bunkerweb:
|
|
tag: 1.6.6
|
|
|
|
# Scheduler settings
|
|
scheduler:
|
|
tag: 1.6.6
|
|
extraEnvs:
|
|
# Enable real IP module to get real IP of clients
|
|
- name: USE_REAL_IP
|
|
value: "yes"
|
|
|
|
# Controller settings
|
|
controller:
|
|
tag: 1.6.6
|
|
|
|
# UI settings
|
|
ui:
|
|
tag: 1.6.6
|