You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the value for the access-log is invalid, the config map obj does not show error/warning state. The error is only visible in the NIC log, for example:
E20240809 10:59:06.679467 1 configmaps.go:212] Configmap nginx-ingress/nginx-config: Invalid value for key access-log: "ssyslog:server=localhost:514"
config-map:
...
Data
====
access-log-off:
----
true
access-log:
----
syslog:server=localhost:514
...
The main idea is to improve UX and allow users to see that objects are not applied due errors by checking (describing) the obj without a need to check NIC logs.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This idea is a follow up of this PR: #5648
If the value for the
access-log
is invalid, the config map obj does not show error/warning state. The error is only visible in the NIC log, for example:config-map:
... Data ==== access-log-off: ---- true access-log: ---- syslog:server=localhost:514 ...
The main idea is to improve UX and allow users to see that objects are not applied due errors by checking (describing) the obj without a need to check NIC logs.
Beta Was this translation helpful? Give feedback.
All reactions