Support zone mode

[lahabana]

Description

With kumahq/kuma#8190 we'll have the GUI in a zone. This means that the GUI should support this. There will likely be NO difference between standalone and zone GUI as zone is the future of Zone.

We may add a page to show KDS connection state of something like this.

[kleinfreund]

In #1875, I’m adding the zone entry to our translation files so that the UI at least renders in zone mode.

[johncowen]

GUI follow up taken from the review of #1875 (comment)

Once this is in could we do another PR with the following:

Wherever this is needed can we make it look for common.product.mode first and if not use a defaultMessage of t(http.api.values.${mode})? Let me know if thats problematic for any reason tho.

We should also probably do this for environment aswell (and anything else that is using backend not-quite-http-values)

[kleinfreund]

Edit: The following comment is outdated. Specifically, the Zone in zone mode will actually have a name and so we decided to keep the URL structure used in global mode.

---

Some more notes:

• In zone mode, show Zone in the sidebar navigation instead of Zones (global) or Zone Egresses (standalone) that goes to the URL /zone
• The URL /zone goes to a dedicated Zone detail view that’s different from the regular Zone detail view (name TBD)

  • Question: Does the zone have a name?

    Answer: No

• Overview data comes from a new endpoint, Config tab comes from /config, Ingresses/Egresses are the same

[lahabana]

xref:

• ZoneInsight in the Zone kuma#8523

[lahabana]

There's an extra field called: zone_instance_id that can be present (it's new so it dpends). Probably worth showing

[kleinfreund]

Notes:

• The "name" of the Zone in zone mode is in /config (see https://github.com/kumahq/kuma/blob/75d22f0e6d5988bdd81c7bbd0a2e148333ae3487/pkg/config/app/kuma-cp/kuma-cp.defaults.yaml#L507)
  • Issue for adding this value to the index.html template config: Zone mode: Add Zone name to config object injected into index.html template kuma#8767
• /config includes whether KDS is enabled (see https://github.com/kumahq/kuma/blob/75d22f0e6d5988bdd81c7bbd0a2e148333ae3487/pkg/config/app/kuma-cp/kuma-cp.defaults.yaml#L509). If it’s not enabled, there isn’t going to be a Zone Insight. If it’s enabled, it behaves like in global mode; however, the subscriptions data is different.

[kleinfreund]

xref: kumahq/kuma#8767

[kleinfreund]

We changed our mind on this again and will do the following on the UI side:

• global mode: nothing changes
• zone mode + KDS enabled: nothing changes, the GUI will be disabled on the backend side
• zone mode + KDS disabled: make everything behave like standalone mode behaves currently (essentially, replace mentions of standalone with zone, i.e. deprecate standalone mode)