-
Notifications
You must be signed in to change notification settings - Fork 213
Description
Environment
Chart: haproxytech/kubernetes-ingress
haproxytech/kubernetes-ingress:3.1.14
Kubernetes Version: (AKS v1.31.1)
Installation Method: Helm
Issue Description:
When deploying HAProxy Ingress Controller 3.1.14 via Helm, the controller logs show continuous failures related to map file creation/updates. It reports that the maps directory does not exist or is not configured. This happens immediately after pod startup, before any Ingress resources are created.
Error Logs
2025/11/24 02:12:07 INFO haproxy/rules/main.go:166 [transactionID=4bd2734f-876d-4de9-ad34-ccb6b3f10e7b] reload required : New HAProxy rule 'REQ_SET_VAR' cr │
│ eated │
│ 2025/11/24 02:12:07 INFO haproxy/rules/main.go:166 [transactionID=4bd2734f-876d-4de9-ad34-ccb6b3f10e7b] reload required : New HAProxy rule 'REQ_SET_VAR' cr │
│ eated │
│ 2025/11/24 02:12:07 INFO haproxy/rules/main.go:166 [transactionID=4bd2734f-876d-4de9-ad34-ccb6b3f10e7b] reload required : New HAProxy rule 'REQ_SET_VAR' cr │
│ eated │
│ 2025/11/24 02:12:07 INFO haproxy/maps/main.go:172 [transactionID=4bd2734f-876d-4de9-ad34-ccb6b3f10e7b] reload required : Runtime update of map file 'path-p │
│ refix-exact' failed : error preparing map file: maps dir doesn't exist or not specified. Either use maps-dir CLI option or reload HAProxy if map section exi │
│ sts in config file │
│ 2025/11/24 02:12:07 INFO haproxy/maps/main.go:172 [transactionID=4bd2734f-876d-4de9-ad34-ccb6b3f10e7b] reload required : Runtime update of map file 'path-p │
│ refix' failed : error preparing map file: maps dir doesn't exist or not specified. Either use maps-dir CLI option or reload HAProxy if map section exists in │
│ config file │
│ 2025/11/24 02:12:07 INFO haproxy/maps/main.go:172 [transactionID=4bd2734f-876d-4de9-ad34-ccb6b3f10e7b] reload required : Runtime update of map file 'sni' f │
│ ailed : error preparing map file: maps dir doesn't exist or not specified. Either use maps-dir CLI option or reload HAProxy if map section exists in config │
│ file │
│ 2025/11/24 02:12:07 INFO haproxy/maps/main.go:172 [transactionID=4bd2734f-876d-4de9-ad34-ccb6b3f10e7b] reload required : Runtime update of map file 'host' │
│ failed : error preparing map file: maps dir doesn't exist or not specified. Either use maps-dir CLI option or reload HAProxy if map section exists in config │
│ file │
│ 2025/11/24 02:12:07 INFO haproxy/maps/main.go:172 [transactionID=4bd2734f-876d-4de9-ad34-ccb6b3f10e7b] reload required : Runtime update of map file 'path-e │
│ xact' failed : error preparing map file: maps dir doesn't exist or not specified. Either use maps-dir CLI option or reload HAProxy if map section exists in │
│ config file │
│ [NOTICE] (69) : Reloading HAProxy │
│ [NOTICE] (69) : Initializing new worker (122) │
│ [NOTICE] (69) : Loading success. │
│ [WARNING] (104) : Proxy https stopped (cumulated conns: FE: 0, BE: 0). │
│ [WARNING] (104) : Proxy http stopped (cumulated conns: FE: 0, BE: 0). │
│ [WARNING] (104) : Proxy healthz stopped (cumulated conns: FE: 0, BE: 0). │
│ [WARNING] (104) : Proxy stats stopped (cumulated conns: FE: 0, BE: 0). │
│ 2025/11/24 02:12:07 INFO controller/controller.go:241 [transactionID=4bd2734f-876d-4de9-ad34-ccb6b3f10e7b] HAProxy reloaded │
│ [NOTICE] (69) : haproxy version is 3.1.9-38cc406 │
│ [WARNING] (69) : Former worker (104) exited with code 0 (Exit) │
│ 2025/11/24 02:12:08 INFO k8s/crs-monitor.go:107 Custom resource definition created, adding CR watcher for Defaults │
│ 2025/11/24 02:12:13 INFO k8s/crs-monitor.go:107 Custom resource definition created, adding CR watcher for Global │
│ 2025/11/24 02:12:18 INFO k8s/crs-monitor.go:107 Custom resource definition created, adding CR watcher for Backend │
│ 2025/11/24 02:12:23 INFO k8s/crs-monitor.go:107 Custom resource definition created, adding CR watcher for TCP