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
After federating to the global CP, I can see the following log entries. But the policies flowed well from global to zone and vice versa; I can also see the zone shown as "online" on the GUI.
We need to analyze whether this is a doc issue or a defect in the product.
2024-10-11T09:24:26.222Z ERROR kds-zone failed to flush zone status {"zone": "zone-fed", "error": "Resource not found: type=\"Zone\" name=\"zone-fed\" mesh=\"\""}
2024-10-11T09:24:26.225Z INFO defaults ensuring Zone resource exists {"name": "zone-fed"}
2024-10-11T09:24:26.225Z INFO defaults detected Zone resource with different name than Zone CP name. Deleting. This might happen if you change the name of the Zone CP {"name": "zone-fed"}
The text was updated successfully, but these errors were encountered:
What happened?
By following this guide, https://kuma.io/docs/2.8.x/guides/federate/ we can federate a zone CP to a global CP.
After federating to the global CP, I can see the following log entries. But the policies flowed well from global to zone and vice versa; I can also see the zone shown as "online" on the GUI.
We need to analyze whether this is a doc issue or a defect in the product.
The text was updated successfully, but these errors were encountered: