Manage all your services
Organize developers and permissions
Empower your developers
Autonomously identify issues
Native Kubernetes Ingress Controller
Instantly implement policies
Monitor your Kong Enterprise
API Design and Testing
Ingress and CRDs
Kong Gateway and Enterprise features
Accelerate your journey into microservices
Empower teams to provide security, governance and
Rapidly design, publish and consume APIs and services
Take control of your microservices with the world’s most
popular API gateway
Own your Kubernetes cluster by using Kong as an Ingress
Build, secure and observe your modern Service Mesh
decK can construct a state by combining multiple JSON or YAML files inside a
directory instead of a single file.
In most use cases, a single file will suffice, but you might want to use
multiple files if:
You can specify an entire directory for decK to consume using the --state
You can also specify multiple files using comma-separated syntax (--state file.yml,file2.yml,directory),
or by using the flag many times (-s file.yml -s file2.yml -s directory)
-s file.yml -s file2.yml -s directory
Under the hood, decK combines the YAML/JSON files in a very dumb fashion,
meaning it just concatenates the various arrays in the file together, before
starting to process the state.
There is no automated way of generating multiple files using decK. You will
have to export the entire configuration using the deck dump command and then
split the configuration into different files as you see fit for your use case.
Please note that having the state split across different files is not same
as distributed configuration.