New GUI build for 0.6.0

[bloqhead]

Summary

New build files for v0.6.0. This build adds new views for Gateway and Ingress Dataplane types, Remote Control Planes, as well as various features to support the new multicluster mode. This update also includes tons of under-the-hood optimizations for the browser.

Full changelog

• feat: shareable entity links [#35]
• feat: mTLS warning on Traffic Permissions [#38]
• feat: YAML view improvements: added separate tabs for Universal and Kubernetes YAML formatting [#37]
• feat: Multicluster features [#39]
  • Added new endpoints for fetching Gateway and Ingress Dataplanes (caveat: pagination does not yet work for these endpoints)
  • New view for Remote CPs (only enabled in Multicluster mode)
  • Multicluster mode detection features that are accessible across the entire GUI
  • Now displaying a tag next to the status in the top bar that lets the user know when Kuma is running in Multicluster mode
  • Expanded and improved tag handling for all Dataplane views to cover Inbound, Ingress, and Gateway tags
  • Added a new column to the Dataplanes tables that denotes the type of Dataplane (Standard, Ingress, Gateway)
  • Added functionality that detects when Kuma has been upgraded by storing the Kuma version in the browser's Local Storage. It will attempt to reload the page so that the user is viewing the latest GUI if the running version is prior to the version found at https://kuma.io/latest_version

Issues resolved

• fix: K8s DP wizard: the "Next" control is no longer appearing when selecting a Mesh -- this was caused by missing variable that was commented out but not reintroduced in this single view. [#36]
• change: disable the "selected" effect when clicking on a row overview -- in the KTabs component, the tab content has an outline around it when clicked on. This change hides the outline. [#36]
• fix: the Expiration Time on the Certificate Insights tab needs to be displayed as a regular date/time, not a human-readable relative one -- in all other instances of time and date being displayed, it's human-readable and relative. For this instance it simply needed to be the date/time itself with no additional modification. [#36]
• fix / improvement: when there is a new version of Kuma, a force-refresh is required to make the GUI work, otherwise a blank screen is displayed. I was unable to reproduce this but have made multiple changes to try and address it [#36]
  • I've made it so that the version is now stored in localStorage and the app checks the version from Kuma itself against the localStorage one. If they are different, the app updates the localStorage version string, and forces a reload on the page itself.
  • Additionally, I've changed the JS file chunk naming for every route in webpack's configuration. This means that instead of the compiled JS files always being randomized string names that are always completely different after every compile, they are named according to route. e.g. 12345678.js would be renamed to something like traffic-routes.js.
  • In addition to the above, I have also added cache busting to the compiled JS files. So traffic-routes.js turns into traffic-routes?t=1234abcd. This helps ensure that each new version forces the browser to reload the JS files fresh.

NOTE:

⚠️ This release will require a force-refresh in your browser if you are coming from a previous version of Kuma. This is due optimization efforts to the JS and CSS files being namespaced instead of using auto-generated filenames.