Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nano is not a valid timeEncoding configuration for operator and webhooks #575

Open
DaazKu opened this issue Nov 27, 2023 · 0 comments
Open
Labels
bug Something isn't working

Comments

@DaazKu
Copy link

DaazKu commented Nov 27, 2023

The README state that we can use nano as a valid time encoding for:

  • operator ->
    | `logging.operator.timeEncoding` | string | `"rfc3339"` | Logging time encoding for KEDA Operator. allowed values are `epoch`, `millis`, `nano`, `iso8601`, `rfc3339` or `rfc3339nano` |
  • webhook ->
    | `logging.webhooks.timeEncoding` | string | `"rfc3339"` | Logging time encoding for KEDA Operator. allowed values are `epoch`, `millis`, `nano`, `iso8601`, `rfc3339` or `rfc3339nano` |
    (note that it says operator. C/P issue)

Trying to do so results in the following error:

2023-11-27T16:32:51.521594883Z invalid argument "nano" for "--zap-time-encoding" flag: invalid time-encoding value "nano"

Steps to Reproduce the Problem

Use the following to configure the chart:

logging:
  operator:
    level: error
    format: json
    timeEncoding: nano
  metricServer:
    level: 0
    stderrthreshold: ERROR
  webhooks:
    level: error
    format: json
    timeEncoding: nano

Specifications

  • KEDA Version: 2.12.0
@DaazKu DaazKu added the bug Something isn't working label Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant