[Bug]: NIC does not accept day-unit value for controller.mgmt.usageReport.interval

[mrajagopal]

Version

5.0.0

What Kubernetes platforms are you running on?

Kind

Steps to reproduce

Deploy NIC v5.0.0 with alues.yaml that has controller.mgmt.usageReport.interval set to 30d

Observed Error:
E20250630 17:05:38.655714 1 configmaps.go:818] Configmap nginx-plus/ingress-nginx-plus-mgmt: Invalid value for the interval key: got "30d": time: unknown unit "d" in duration "30d". Ignoring. E20250630 17:05:38.655764 1 configmaps.go:824] Configmap nginx-plus/ingress-nginx-plus-mgmt: Value too low for the interval key, got: 30d, need higher than 60s. Ignoring.

Expected Outcome:
A value of 30d for the usage report interval applies successfully in the nginx configuration

Workaround

Use the hours as the units, eg 30 days as 30*24=720h

[github-actions]

Hi @mrajagopal thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

[AlexFenlon]

Hi @mrajagopal,

Thanks for the bug report, I noticed that here we are just using the go standard library for time.ParseDuration in our validation for this. As you mentioned, the most is goes up to is hours, not days or months.

[cpuengr949]

When I try 720h in there I get the following.

stderr: "2025/07/07 17:51:37 [notice] 70#70: js vm init njs: 000055B90A8B5F80\n2025/07/07 17:51:37 [emerg] 70#70: interval cannot be greater than 24h in /etc/nginx/nginx.conf:157\n"

[mrajagopal]

It turns out that the usage_report directive only allows the interval value to be set to a maximum of 24 hours.
Therefore, our recommendation to the customer is to set this to 24h.

Hope this clarifies the limits of controller.mgmt.usageReport.interval parameter.
I have requested the docs to provide limits for the interval value of the usage_report directive in the nginx.org docs.

@AlexFenlon, please confirm if we have assessed this appropriately.
We ought to improve the logging message that NIC writes to indicate the limits of the interval value.
Maybe the schema needs to be update to drop the day resolution as it can only be 1 day as the interval when 24h should suffice.

[vepatel]

@mrajagopal #8043 drops day altogether