Kong Mesh ships with a read-only GUI that you can use to retrieve Kong Mesh resources. By default the GUI listens on the API port and defaults to :5681/gui
.
To access Kong Mesh we need to first port forward to the API with:
kubectl port-forward svc/kong-mesh-control-plane -n kong-mesh-system 5681:5681
And then navigate to 127.0.0.1:5681/gui
to see the GUI.
You will notice that Kong Mesh automatically creates a Mesh
entity with name default
.
You can use Kong Mesh with kubectl
to perform read and write operations on Kong Mesh resources. For example:
kubectl get meshes
# NAME AGE
# default 1m
or you can enable mTLS on the default
Mesh with:
echo "apiVersion: kuma.io/v1alpha1
kind: Mesh
metadata:
name: default
spec:
mtls:
enabledBackend: ca-1
backends:
- name: ca-1
type: builtin" | kubectl apply -f -
You will notice that Kong Mesh automatically creates a Mesh
entity with name default
.
Kong Mesh ships with a read-only HTTP API that you can use to retrieve Kong Mesh resources.
By default the HTTP API listens on port 5681
. To access Kong Mesh we need to first port forward to the API with:
kubectl port-forward svc/kong-mesh-control-plane -n kong-mesh-system 5681:5681
And then you can navigate to 127.0.0.1:5681
to see the HTTP API.
You will notice that Kong Mesh automatically creates a Mesh
entity with name default
.
You can use the kumactl
CLI to perform read-only operations on Kong Mesh resources. The kumactl
binary is a client to the Kong Mesh HTTP API, you will need to first port forward to the API with:
kubectl port-forward svc/kong-mesh-control-plane -n kong-mesh-system 5681:5681
and then run kumactl
, for example:
kumactl get meshes
# NAME mTLS METRICS LOGGING TRACING
# default off off off off
You can configure kumactl
to point to any zone kuma-cp
instance by running:
kumactl config control-planes add --name=XYZ --address=http://{address-to-kuma}:5681
You will notice that Kong Mesh automatically creates a Mesh
entity with name default
.