Where Does Kong Gateway Store Config?
Kong Gateway reads /etc/kong/kong.conf with declarative kong.yml config plus a Postgres database backend.
Last updated
Kong Gateway configures through kong.conf plus a declarative file or database. Default conf lives under /etc/kong with docs inline. DB-less mode reads kong.yml for routes and plugins. Database mode adds Postgres with migrations.
Files suit single nodes and containers. Databases suit clusters sharing routes. Admin API and Manager ports expose control on localhost by default. Keep secrets out of files with vault references.
Where Kong Gateway stores this, by platform
/etc/kong/kong.conf (declarative /etc/kong/kong.yml, Postgres for DB mode)
Main conf plus declarative YAML or Postgres. Migrations bootstrap the schema. Env vars override files in Docker. Keep DB credentials outside the repo.
Frequently asked questions
How do I move Kong to a new server?
Copy kong.conf plus kong.yml and point the new host at the same Postgres. Migrations bootstrap the schema there. Env vars override files for container runs.
How do I run Kong without a database?
Mount a kong.yml at the declarative path and set database off. Routes, services and plugins load from the file. Use Postgres mode when plugins need central coordination.
Notice an outdated path? Let us know.