The Microgateway Engine is built based on the Envoy proxy and enriched with Airlock-specific features. It may be useful to investigate the underlying Envoy configuration for complex problems.
To simplify this task we have created a CustomResource EnvoyConfiguration
which contains the Envoy configuration.
The CustomResource EnvoyConfiguration
is not intended to be created or changed manually. This resource is composed of the other Airlock Microgateway CustomResources and will be overwritten by the Airlock Microgateway Operator.
The following example shows the output of such a CustomResource:
- Description:
Spec.Envoy Resources Raw
– Contains the base64-encoded Zstandard-compressed Envoy configuration.Status.Conditions
– Shows whether the configuration is synchronized/active on Airlock Engine.Status.Xds
– Shows the different Envoy resources and their status.
The base64-encoded content can be decoded to JSON format as follows:
kubectl get envoyconfiguration <name> -ojsonpath='{.spec.envoyResourcesRaw}' | base64 -d | zstd -d | jq
For the above command, the CLI tools zstd
and jq
must be installed on your system.