A sync-status log for Connectors and Listeners should be triggered in any Skupper-related pod

[vsomwanshi]

Describe the bug The sync-status log for connectors and listeners must be initiated within any Skupper pod — potentially the controller pod.

I see skupper-controller gives the information about the site 'Basically why it is failing e.g configmaps "skupper-router" not found`. We can check the runtime status of connectors and listeners using commands but suppose someone wants to reverify the previous state of listeners then where should we can check ?

Scenario:

Here is the case for reference : https://github.com/skupperproject/skupper/issues/2323

1] We had an issue etcd server related issue in our OpenShift cluster. I noticed that in one of the site listener was failing with some etcd server related issue only but since i don't have old logs unable to get the error statement.

2] Then i deleted that listener from the site somehow it was still stuck in pending for long time.

3] To address this issue, i deleted that site entirely and recreated it somehow site is failing to create with error. I have raised a support case with RedHat support team to check etcd related error but somehow i don't have that concrete error statement to share it with support team.

$ oc get site

NAME                  STATUS   SITES IN NETWORK   MESSAGE
SRE   Error                       configmaps "skupper-router" not found

Steps to reproduce:

skupper delete site --all -n namespace Create site ( apply site yaml configuration file )

How To Reproduce N/A

Expected behavior The sync-status log for connectors and listeners must be initiated within any Skupper pod — potentially the controller pod.

Environment details

• Skupper CLI: 2.1.0
• Skupper Operator (if applicable): N.A
• Platform: OpenShift

Additional context N/A