kuma-gui
kuma-gui copied to clipboard
Consider showing Mesh config in inbound/outbound drawers
Description
The drawers for inbounds/outbounds are supposed to show you the entire "picture" of the policies/config for a dataplane.
We currently use the inspect _rules
API to show us the merged result of policy configs, but occasionally this doesn't show the entire picture. For example, MeshTLS
can take the mode
from the config for the Mesh for its default, but this is not currently shown in the resulting config for a MeshTLS
policy.
Moreover if an inbound/outbound has no policies associated with it at all, there are still things take from the Mesh config that influence the traffic.
Therefore we should consider:
- Showing the Mesh config at the bottom of the drawer underneath all of the rules. That way the user can also see any defaults that are being used for the Mesh (we might want to remove the
type
andname
from the display of this config seeing as thats already clear) - Separately, there is a decision to be made on whether the inspect API
_rules
endpoint should show the full result of a policy which can be influenced by the configuration for the Mesh, such as in the case of MeshTLS wheremode
might take 'PERMISSIVE' from the Mesh config. If this change happens, we will need to be able to include this in the GUI somehow underOrigins
(currentlyOrigin Policies
so you can understand where this configuration comes from.