You are browsing documentation for an outdated version.
See the latest documentation here.
Prepare to Administer Kong Gateway
Before getting started with using Kong Gateway, verify that it was
installed correctly, and that you’re ready to administer it.
Before you begin
Before you start this section, make sure that:
- Kong Gateway is installed and running.
- Kong Manager (if applicable) and Kong Admin API ports are listening on the
appropriate port/IP/DNS settings.
- If using declarative configuration to configure Kong Gateway,
decK is installed.
In this guide, an instance of Kong Gateway is referenced via
<admin-hostname>. Make sure to replace
<admin-hostname> with the hostname
of your control plane instance.
Verify the Kong Gateway configuration
(Optional) Verify Control Plane and Data Plane connection
If you’re running Kong Gateway in hybrid mode,
you need to perform all tasks in this guide from the control plane. You can check
that all of your configurations are being pushed from the control plane to your
data planes using the Cluster Status CLI.
Run the following from a control plane:
The output shows all of the connected data plane instances in the cluster:
Summary and next steps
In this section, you learned about the methods of administering
Kong Gateway and how to access its configuration. Next, go on to
learn about exposing your services with Kong Gateway.