Kusk CLI deploys API gateway configuration from an OpenAPI definition into a Kusk gateway running in Kubernetes. Routing is declared with the x-kusk vendor extension, keeping upstream details alongside the API contract. section 9.4.5
Kusk CLI
Kusk CLI is a command-line tool for deploying and managing Kusk API Gateway configuration.
How Automating API Delivery covers it
- How deep it goes
- Shows installation, cluster setup, port forwarding, artifact deployment, status checks, and conformance testing, but not CLI internals.
- Examples
- Uses a Product Catalog API, x-kusk routing, minikube, port 9000 forwarding, and Portman/Newman conformance tests.
- What it assumes
- Assumes an OpenAPI definition, a versioned API artifact, Kubernetes access, and a CI runner capable of installing command-line tools.
- What you can do after
- Operate/configure a Kusk gateway in a pipeline and deploy a versioned API artifact for subsequent status and conformance checks.
- How it connects
- Connects OpenAPI, Kubernetes, Envoy, minikube, kubectl, port forwarding, and API conformance testing.
This explainer was generated by Manning's knowledge graph from the text of Automating API Delivery. The section links point to the parts of the book it draws on.