OpenShift · Schema
TLSConfig
TLS configuration for the route. Determines how TLS connections are handled at the router.
CI/CDCloud-NativeContainersDevOpsEnterpriseKubernetesPlatform-as-a-Service
Properties
| Name | Type | Description |
|---|---|---|
| termination | string | Indicates termination type. Edge terminates TLS at the router, passthrough forwards encrypted traffic to the backend, and re-encrypt terminates at the router and re-encrypts to the backend. |
| certificate | string | PEM-encoded certificate for the route. Required for edge and re-encrypt termination if not using a default certificate. |
| key | string | PEM-encoded private key for the route certificate. |
| caCertificate | string | PEM-encoded CA certificate chain used to verify client certificates. |
| destinationCACertificate | string | PEM-encoded CA certificate used to verify the backend server certificate. Only applicable for re-encrypt termination. |
| insecureEdgeTerminationPolicy | string | Policy for handling insecure (HTTP) traffic when TLS is configured. None disables insecure traffic, Allow permits it, Redirect sends a 301 redirect to the HTTPS URL. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/TLSConfig",
"title": "TLSConfig",
"type": "object",
"description": "TLS configuration for the route. Determines how TLS connections are handled at the router.",
"properties": {
"termination": {
"type": "string",
"description": "Indicates termination type. Edge terminates TLS at the router, passthrough forwards encrypted traffic to the backend, and re-encrypt terminates at the router and re-encrypts to the backend.",
"enum": [
"edge",
"passthrough",
"reencrypt"
],
"example": "edge"
},
"certificate": {
"type": "string",
"description": "PEM-encoded certificate for the route. Required for edge and re-encrypt termination if not using a default certificate.",
"example": "example_value"
},
"key": {
"type": "string",
"description": "PEM-encoded private key for the route certificate.",
"example": "example_value"
},
"caCertificate": {
"type": "string",
"description": "PEM-encoded CA certificate chain used to verify client certificates.",
"example": "example_value"
},
"destinationCACertificate": {
"type": "string",
"description": "PEM-encoded CA certificate used to verify the backend server certificate. Only applicable for re-encrypt termination.",
"example": "example_value"
},
"insecureEdgeTerminationPolicy": {
"type": "string",
"description": "Policy for handling insecure (HTTP) traffic when TLS is configured. None disables insecure traffic, Allow permits it, Redirect sends a 301 redirect to the HTTPS URL.",
"enum": [
"None",
"Allow",
"Redirect"
],
"example": "None"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/openshift-tlsconfig"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.