Emissary-Ingress TLSContext API
Operations for managing TLSContext custom resources that define reusable TLS configuration including certificates, cipher suites, minimum protocol versions, and client certificate validation settings.
Emissary-Ingress TLSContext API is one of 6 APIs that Emissary-Ingress publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 1 JSON Schema definition.
Tagged areas include TLSContext. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, an API reference, a changelog, authentication docs, and 1 JSON Schema.
This API exposes 4 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version 3.9.0.
Requests are made against a single base URL, https://{kubernetes-api-server}.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 4
Across 2 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Operations for managing TLSContext custom resources that define reusable TLS configuration including certificates, cipher suites, minimum protocol versions, and client certificate…
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are TLSContextSpec (11 properties), ObjectMeta (8 properties), TLSContext (4 properties), TLSContextList (4 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Emissary-Ingress 5
Other APIs Emissary-Ingress publishes across the network.