Start Kong Gateway
One quick way to get Kong Gateway up and running is by using Docker with a PostgreSQL database. We recommend this method to test out basic Kong Gateway functionality.
For a comprehensive list of installation options, see our .
Create a Docker network:
Run a PostGreSQL container:
--network=kong-net \
-p 5432:5432 \
-e "POSTGRES_USER=kong" \
-e "POSTGRES_DB=kong" \
-e "POSTGRES_PASSWORD=kong" \
Prep your database:
Start Kong:
docker run -d --name kong \
--network=kong-net \
-e "KONG_DATABASE=postgres" \
-e "KONG_PG_HOST=kong-database" \
-e "KONG_PG_PASSWORD=kong" \
-e "KONG_CASSANDRA_CONTACT_POINTS=kong-database" \
-e "KONG_PROXY_ACCESS_LOG=/dev/stdout" \
-e "KONG_ADMIN_ACCESS_LOG=/dev/stdout" \
-e "KONG_PROXY_ERROR_LOG=/dev/stderr" \
-e "KONG_ADMIN_LISTEN=0.0.0.0:8001, 0.0.0.0:8444 ssl" \
-p 8000:8000 \
-p 8443:8443 \
-p 127.0.0.1:8001:8001 \
kong:latest
Navigate to
http://localhost:8001/
.
By default, Kong listens on the following ports:
8000
: listens for incomingHTTP
traffic from your clients, and forwards it to your upstream services.8001
: Admin API listens for calls from the command line overHTTP
.8443
: listens for incoming HTTPS traffic. This port has a similar behavior to8000
, except that it expectsHTTPS
traffic only. This port can be disabled via the configuration file.8444
: listens for traffic.
Stop Kong Gateway using the stop command:
Reload Kong Gateway using the command:
kong reload
Start Kong Gateway using the start command:
Now that you have Kong Gateway running, you can interact with the Admin API.