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
Is your feature request related to a problem? Please describe.
We schedule the pod to remote cluster and as we have multiple mutation webhooks which will patch the original pod spec outside liqo webhook. It can happen pod spec is wrong due to the patches and currently the way to debug is to check lido-controller logs and search for it.
Describe the solution you'd like
The perfect solution is to add error events to ShadowPod resource. It will be much easier to debug the issue.
Bonus - When remote liqo controller not able to create pod due to pod spec error, can we report back the status to local cluster the error and stop trying? Currently local cluster just show Pending status.
Describe alternatives you've considered
Currently we look into multiple pod logs to figure out the error.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We schedule the pod to remote cluster and as we have multiple mutation webhooks which will patch the original pod spec outside liqo webhook. It can happen pod spec is wrong due to the patches and currently the way to debug is to check lido-controller logs and search for it.
Describe the solution you'd like
The perfect solution is to add error events to ShadowPod resource. It will be much easier to debug the issue.
Bonus - When remote liqo controller not able to create pod due to pod spec error, can we report back the status to local cluster the error and stop trying? Currently local cluster just show Pending status.
Describe alternatives you've considered
Currently we look into multiple pod logs to figure out the error.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: