Skip to content

Automatic API deployment

Kusk Gateway supports automatic configuration and deployment of an API based on kusk-gateway annotations on your Kubernetes Service resource, allowing you to totally automate the deployment of your API to Kusk Gateway whenever you update deploy the corresponding Service to your cluster.

The following annotations are available:

Name Description Optional
kusk-gateway/openapi-url the absolute URL to the OpenAPI definition to deploy
kusk-gateway/envoy-fleet which EnvoyFleet to use X
kusk-gateway/path-prefix: which path your API will be hosted at X
kusk-gateway/path-prefix-substitution what to substitute the prefix with when forwarding the request to the service X

For example, assuming that you have already set up a deployment that is running your REST API, you could deploy the following Kubernetes Service: 

apiVersion: v1
kind: Service
metadata:
  name: my-api
  annotations:
    kusk-gateway/openapi-url: https://some-resolvablehost-name/path-to-openapi.yaml
spec:
  type: ClusterIP
  selector:
    app: my-api 
  ports:
    - port: 3000
      targetPort: http

Deploying this manifest with kubectl (kubectl apply -f svc.yaml) will make Kusk Gateway automatically

  • read the OpenAPI definition from the openapi-url annotation
  • add corresponding x-kusk.upstream extensions to route API requests to this Service (if not already present)
  • create an API resource for the OpenAPI definition and deploy it to Kusk Gateway

If you want to customize the mapping and/or envoy-fleet used by the API you can add these as annotations also:

apiVersion: v1
kind: Service
metadata:
  name: my-api
  annotations:
    kusk-gateway/openapi-url: https://gist.githubusercontent.com/jasmingacic/082849b29d0e06e5f018a66f4cd49ec3/raw/e91c94cc82e7591031399e0d8c563d28a62de460/openapi.yaml
    kusk-gateway/path-prefix: /my-api
    kusk-gateway/path-prefix-substitution: ""
    kusk-gateway/envoy-fleet: my-private-fleet
spec:
  type: ClusterIP
  selector:
    app: my-api # aforementioned selector
  ports:
    - port: 3000
      targetPort: http