Soon, all Red Hat OpenShift documentation will only be available on docs.redhat.com, the official location of all Red Hat product documentation. Get familiar with the updated experience today!
  1. Documentation
×

Binding [core/v1]

Description

Binding ties one object to another; for example, a pod is bound to a node by a scheduler. Deprecated in 1.7, please use the bindings subresource of pods instead.

Type

object

Required

  • target

Specification

Property Type Description

.apiVersion

string

APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources

.kind

string

Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds

.metadata

ObjectMeta meta/v1

Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata

.target

ObjectReference core/v1

The target object that you want to bind to the standard object.

API endpoints

The following API endpoints are available:

  • /api/v1/namespaces/{namespace}/bindings

    • POST: create a Binding

/api/v1/namespaces/{namespace}/bindings

Table 1. Global path parameters
Parameter Type Description

namespace

string

object name and auth scope, such as for teams and projects
Table 2. Global guery parameters
Parameter Type Description

pretty

string

If 'true', then the output is pretty printed.
HTTP method

POST

Description

create a Binding

Table 3. Body parameters
Parameter Type Description

body

Binding core/v1
Table 4. HTTP responses
HTTP code Reponse body

200 - OK

Binding core/v1

201 - Created

Binding core/v1

202 - Accepted

Binding core/v1

401 - Unauthorized

Empty