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
I'm able to see the display message for my checks in the UI, but not using the kubernetes CLI. Is that expected? I see an errorMessage and message field in the status of my Canary, but cannot get anything to display. Neither field appears to be populated regardless of if I've setup a custom display message.
For example, I can use k get canary kube-system-checks -o json and see:
In that example I have a display message defined, but I never see anything in status.message or status.errorMessage. It would be helpful to see some information there so that when a check succeeds I can tell which resources it found and when it fails I can see which resources weren't healthy.
This seems to be true of many check types, not just kubernetes checks.
The text was updated successfully, but these errors were encountered:
It looks like the describe command isn't giving me any messages either. Is this a bug? I would expect to be able to see whatever we've defined in the display.expr to show up somewhere regardless of if the check is passing or failing. When we're troubleshooting failing checks or developing new checks it is helpful to be able to output information for debugging purposes.
I'm able to see the display message for my checks in the UI, but not using the kubernetes CLI. Is that expected? I see an
errorMessage
andmessage
field in the status of myCanary
, but cannot get anything to display. Neither field appears to be populated regardless of if I've setup a custom display message.For example, I can use
k get canary kube-system-checks -o json
and see:In that example I have a display message defined, but I never see anything in
status.message
orstatus.errorMessage
. It would be helpful to see some information there so that when a check succeeds I can tell which resources it found and when it fails I can see which resources weren't healthy.This seems to be true of many check types, not just
kubernetes
checks.The text was updated successfully, but these errors were encountered: