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

bug: unknown field "status.conditions[0].lastTransitionTime" is constantly displayed in logs #2259

Open
ikatlinsky opened this issue Jul 9, 2024 · 4 comments
Labels

Comments

@ikatlinsky
Copy link
Contributor

ikatlinsky commented Jul 9, 2024

Current Behavior

Logs of the ingress controller is full of messages unknown field "status.conditions[0].lastTransitionTime"

Expected Behavior

I see not reason to display this message, as it makes logs less usable

Error Logs

W0709 14:51:15.702623       1 warnings.go:70] unknown field "status.conditions[0].lastTransitionTime"
W0709 14:51:20.470542       1 warnings.go:70] unknown field "status.conditions[0].lastTransitionTime"

Steps to Reproduce

  1. create route and upstream using crd and ingress controller
  2. inspect logs

Environment

  • APISIX Ingress controller version: 1.8.2
  • Kubernetes cluster version (run kubectl version): v1.29.5
@ikatlinsky
Copy link
Contributor Author

@Revolyssup hi! would be nice if that can be addressed in the same way as #2206, current logging approach makes it barely usable for alerting staff, as too many false positive errors are shown, thanks

Copy link

github-actions bot commented Oct 8, 2024

This issue has been marked as stale due to 90 days of inactivity. It will be closed in 30 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions.

@github-actions github-actions bot added the stale label Oct 8, 2024
@ikatlinsky
Copy link
Contributor Author

Fix is still desired

@github-actions github-actions bot removed the stale label Oct 12, 2024
Copy link

This issue has been marked as stale due to 90 days of inactivity. It will be closed in 30 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant