API Bindings

Bindings are the last crucial compontent for exposing resources via the Cup API. A binding defines which resource types should be exposed via the API, and what controller should handle their operations.

{
  "apiVersion": "cup.flipt.io/v1alpha1",
  "kind": "Binding",
  "metadata": {
    "name": "flipt"
  },
  "spec": {
    "controller": "flipt",
    "resources": [
      "flipt.io/v1alpha1/flags",
      "flipt.io/v1alpha1/segments"
    ]
  }
}

Specification

Binding

Each controller resource definition has the following top-level fields. Both apiVersion and kind are fixed constants, but metadata and spec can be configured accordingly.

Metadata

API bindings have a single metadata string field name. Each configured binding should be uniquely named.

BindingSpec

The API binding spec binds a Controller to handle a set of Resource Definitions. A single definitions registers all the declared resources on the cupd API (under /apis). Each resource will be handled by the named controller.