Skip to content
Kong Logo | Kong Docs Logo
search
  • We're Hiring!
  • Docs
    • Kong Gateway
    • Kong Konnect
    • Kong Mesh
    • Plugin Hub
    • decK
    • Kubernetes Ingress Controller
    • Insomnia
    • Kuma

    • Docs contribution guidelines
  • Plugin Hub
  • Support
  • Community
  • Kong Academy
Early Access
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Plugin Hub
  • decK
  • Kubernetes Ingress Controller
  • Insomnia
  • Kuma

  • Docs contribution guidelines
  • 1.17.x (latest)
  • 1.16.x
  • 1.15.x
  • 1.14.x
  • 1.13.x
  • 1.12.x
  • 1.11.x
  • 1.10.x
  • 1.9.x
  • 1.8.x
  • 1.7.x
  • pre-1.7
    • Terminology
    • Architecture
    • Compatibility Promise
    • Getting Started with decK
    • Backup and Restore
    • Upgrade to Kong Gateway 3.x
    • Configuration as Code and GitOps
    • Distributed Configuration
    • Best Practices
    • Using decK with Kong Gateway (Enterprise)
    • Using decK with Konnect
    • Run decK with Docker
    • Using Multiple Files to Store Configuration
    • De-duplicate Plugin Configuration
    • Set Up Object Defaults
    • Using environment variables with decK
    • deck completion
    • deck convert
    • deck diff
    • deck dump
    • deck ping
    • deck reset
    • deck sync
    • deck validate
    • deck version

github-edit-pageEdit this page

report-issueReport an issue

enterprise-switcher-iconSwitch to OSS

On this page
  • Manage a subset of configuration
decK
1.15.x
  • Home
  • decK
  • Guides
  • Backup Restore
  • Backup and Restore of Kong's Configuration
You are browsing documentation for an outdated version. See the latest documentation here.

Backup and Restore of Kong's Configuration

You can use decK to back up and restore a subset or the entirety of Kong’s configuration.

To back up Kong’s configuration, use the dump command:

$ deck dump
# this generates a kong.yaml file with the entire configuration of Kong

Then, restore this file back to Kong using the sync command:

$ deck diff # a dry-run where decK shows the changes it will perform
$ deck sync # actually re-creates the entities in Kong

Manage a subset of configuration

You can export/import/manage a subset of Kong’s configuration using decK’s select-tag feature. This is similar to adopting distributed configuration for Kong.

The select-tag feature assumes that all the entities you would like to manage in Kong share a common tag(s).

Assuming you have such a common tag (for example, let’s call it foo-tag), you can use it to export only a subset of the configuration:

deck dump --select-tag foo-tag

If you observe the file generated by decK, you will see the following section:

_info:
  select_tags:
  - foo-tag

This subsection tells decK to filter out entities containing select-tags during a sync operation.

Now, you can manage or sync back only this subset of Kong’s configuration.

Thank you for your feedback.
Was this page useful?
  • Kong
    THE CLOUD CONNECTIVITY COMPANY

    Kong powers reliable digital connections across APIs, hybrid and multi-cloud environments.

    • Company
    • Customers
    • Events
    • Investors
    • Careers Hiring!
    • Partners
    • Press
    • Contact
  • Products
    • Kong Konnect
    • Kong Gateway
    • Kong Mesh
    • Get Started
    • Pricing
  • Resources
    • eBooks
    • Webinars
    • Briefs
    • Blog
    • API Gateway
    • Microservices
  • Open Source
    • Install Kong Gateway
    • Kong Community
    • Kubernetes Ingress
    • Kuma
    • Insomnia
  • Solutions
    • Decentralize
    • Secure & Govern
    • Create a Dev Platform
    • API Gateway
    • Kubernetes
    • Service Mesh
Star
  • Terms•Privacy
© Kong Inc. 2023