No rule is applied on k8s env

[yacinebbt]

Hello there,

I've deployed bunkerweb 1.5.10 on a kubernetes environnement

i am not able to deploy any rules from the list below

I tried to apply different rules such as, Antibot ( choosing also multiple options, captcha, recaptcha, hcaptcha...), Auth basic, Country, Blacklist... but none of them worked.

even though the bunkerweb-ui shows a success

then later, i upgraded the bunkerweb version from 1.5.10 to 1.5.12, and everything works just fine, yet no rule can be applied on services.
you can see clearly the stat of pods are running without any issue

Debugging
here is an exemple of log entry from bunkerweb-ui pod when activating a rule:

[2025-01-22 10:59:13 +0000] [UI] [9] [⚠️ ] - {'USE_ANTIBOT': 'turnstile', 'REVERSE_PROXY_URL_1': '/', 'REVERSE_PROXY_HEADERS_1': '', 'REVERSE_PROXY_HEADERS_CLIENT_1': '', 'REVERSE_PROXY_BUFFERING_1': 'yes', 'REVERSE_PROXY_AUTH_REQUEST_1': '', 'REVERSE_PROXY_AUTH_REQUEST_SIGNIN_URL_1': '', 'REVERSE_PROXY_AUTH_REQUEST_SET_1': '', 'REVERSE_PROXY_CONNECT_TIMEOUT_1': '60s', 'REVERSE_PROXY_READ_TIMEOUT_1': '60s', 'REVERSE_PROXY_SEND_TIMEOUT_1': '60s', 'REVERSE_PROXY_INCLUDES_1': '', 'SERVER_NAME': 'xx.yyyyyy.zz'}

i configured the log level in the bunkerweb pods ( generated from the Daemonset) to info, but i can't see any important informations:

2025/01/22 12:21:39 [info] 1702995#1702995: *350719 [CLUSTERSTORE] redis reused times = 0, context: ngx.timer
2025/01/22 12:21:39 [info] 1702995#1702995: *350719 [CACHESTORE] hit level for dns_2.0.0.127.bl.blocklist.de = 3, context: ngx.timer
2025/01/22 12:21:39 [info] 1702995#1702995: *350719 [CACHESTORE] hit level for dns_2.0.0.127.xbl.spamhaus.org = 3, context: ngx.timer
2025/01/22 12:21:39 [notice] 1702995#1702995: *350719 [DNSBL] dnsbl check for xbl.spamhaus.org is successful, context: ngx.timer
2025/01/22 12:21:39 [info] 1702995#1702995: *350719 [CACHESTORE] hit level for dns_2.0.0.127.sbl.spamhaus.org = 3, context: ngx.timer
2025/01/22 12:21:39 [notice] 1702995#1702995: *350719 [DNSBL] dnsbl check for sbl.spamhaus.org is successful, context: ngx.timer
2025/01/22 12:21:39 [info] 1702995#1702995: *350719 [CACHESTORE] hit level for dns_2.0.0.127.problems.dnsbl.sorbs.net = 3, context: ngx.timer
2025/01/22 12:21:39 [error] 1702995#1702995: *350719 [DNSBL] dnsbl check for problems.dnsbl.sorbs.net failed, context: ngx.timer
2025/01/22 12:21:39 [notice] 1702995#1702995: *350719 [DNSBL] dnsbl check for bl.blocklist.de is successful, context: ngx.timer
2025/01/22 12:21:39 [info] 1702995#1702995: *350719 [INIT-WORKER] dnsbl:init_worker() call successful : success, context: ngx.timer
2025/01/22 12:21:39 [info] 1702995#1702995: *350719 [INIT-WORKER] called init_worker() methods of plugins, context: ngx.timer
2025/01/22 12:21:39 [info] 1702995#1702995: *350719 [INIT-WORKER] init phase ended, context: ngx.timer
2025/01/22 12:21:39 [notice] 1702995#1702995: *350719 [INIT-WORKER] BunkerWeb is ready to fool hackers ! 🚀, context: ngx.timer

it would be great for me if you have any hints or ideas to how to resolve this issue.

Regards,
Yacine.

[yacinebbt]

here is the k8s repo i am deploying: https://github.com/yacinebbt/bunkerweb-k8s

[TheophileDiot]

Hi @yacinebbt,

Thank you for bringing this up! We are aware of the current issue with autoconf services and the web UI. In the next major release, the ability to edit autoconf-created services via the web UI will be removed. This decision was made because settings modified through the UI are not persistent, due to the underlying way autoconf services function.

This change aligns with the intended design of autoconf services, where all configurations should be defined within annotations and labels. By focusing on this approach, we ensure consistency and prevent potential conflicts or unexpected behaviors.

If you have further questions or need assistance preparing for this change, feel free to reach out!

[yacinebbt]

Hello,

if i will undestand what you're saying, the current version of bunkerweb is not working on a k8s env, is that right? and we need to wait till the next major version of bunkerweb to be able to use bunkerweb on a k8s env?

please correct me if i'm mistaken, thank you.

Regards