Configuration Reports

You may be aware that Workspaces are at the centre of the configuration hierarchy, and configuration is assembled from a range of sources. You can explore the configuration by starting from the Workspaces section of the user interface.

Understand Linking and Dependencies

The Propagation view is a good place to start:

Here, we can view the configuration within the Workspace:

• Default configuration is inherited from the default tenant, typically managed by the platform team
• We can see our workspaces (bookinfo-ws). Each contains Workspace (W) and Gateway Group (G) configuration, indicated with green as the configuration is correctly propagated
• This configuration is then distributed across two Kubernetes clusters, to one or more namespaces (e.g. bookinfo) on each

View Configuration for a Hostname (FQDN)

Alternatively, we can view the configuration as it applies to a hostname (FQDN) we are interested in:

What to look out for

When inspecting the Tetrate platform configuration, you can look out for:

• Is the configuration applied to the expected locations, i.e. namespaces on the expected clusters? Errors here may indicate incorrect specification for Workspaces or Groups, or that the service has been deployed in the wrong location.
• Has the configuration propagated correctly? Are there warnings or errors (highlighted in orange) against components of the configuration. Errors here may indicate mismatched configuration which references resources that are not present in the Workspace or Group.
• Is expected configuration missing, or is configuration present that is not expected? As an example, higher-level configuration (for example, defined at the Tenant or Organization level) will augment and potentially override your Workspace-scoped configuration.

The propagation view will help you to identify the complete Tetrate platform configuration as it applies to your services.