Connection Pipeline
Status: Unavailable at runtime: the current Operator validates and records NexoConnectionPipeline but does not deliver its settings to a runtime container.
:::caution No supported deployment contract
This capability is documented for catalog completeness, but the selected release does not publish a supported end-to-end deployment contract.
:::
Always confirm availability in the release bundle selected for deployment.
At a glance
| Property | Value |
|---|---|
| Pipeline phase | Connection |
| Category | Connection |
| Canonical minimum tier | Free |
| Canonical entitlement | Yes |
| Supported deployment contract | No |
| Release status | Unavailable at runtime: the current Operator validates and records NexoConnectionPipeline but does not deliver its settings to a runtime container. |
Release accuracy
- Current documentation: Unavailable at runtime: the current Operator validates and records NexoConnectionPipeline but does not deliver its settings to a runtime container.
Where any detail below conflicts with the release status above, the release status is authoritative. Field names and examples describe the current dashboard and CRD surface; always confirm behavior against the selected release bundle before relying on it operationally.
Release-aware feature flow. The diagram is explanatory; the release status on this page is authoritative.
Diagram resources: Open the SVG full screen · Download the editable Excalidraw source
Performance impact
:::warning Unverified performance figures
These figures are illustrative only. They are not current benchmarks or service guarantees and have not been verified by the current test suite.
:::
| Percentile | Reported figure |
|---|---|
| P50 | 0ms |
| P95 | 0ms |
| P99 | 0ms |
Note: No runtime performance impact is claimed because the current Operator does not deliver this configuration.
Overview
The dashboard and CRD expose connection-layer TLS, handshake, tenant identity, authentication, connection-limit, and pooling fields. The current Operator resolves and validates the object and includes it in graph-revision metadata, but intentionally omits the unconsumed connection-pipeline configuration from runtime mounts.
A successful apply or Ready status therefore proves schema acceptance, not runtime behavior. Supported listener and upstream TLS are configured on NexoDeploymentProfile.
When to use
- Recording intended future connection policy for schema evaluation
- Inspecting the dashboard and CRD contract without treating it as enforcement
How it works
- NexoProxy references NexoConnectionPipeline through connectionPipelineRef.
- The Operator resolves and validates the referenced object.
- Its content contributes to graph-revision metadata for auditability.
- The Operator does not mount connection-pipeline configuration into ingress or another runtime container.
- No field on this CRD changes current data-plane behavior.
Configuration
“Not specified” means required semantics were not declared for that field.
| Field | Type | Default | Required | Description |
|---|---|---|---|---|
pooling.mode | select | none | Not specified | Schema accepts none, session, and transaction; no mode is delivered to the current runtime |
pooling.maxServerConnections | number | unset | Not specified | Accepted desired-state field with no current runtime effect |
pooling.minIdleConnections | number | unset | Not specified | Accepted desired-state field with no current runtime effect |
pooling.maxConnectionAge | duration | unset | Not specified | Accepted desired-state field with no current runtime effect |
Settings reference
No additional settings reference is documented for this component.
Examples
No example is documented for this component.
Best practices
- Do not use this CRD as evidence that TLS, authentication, tenant isolation, limits, or pooling are active
- Use NexoDeploymentProfile for supported listener and upstream TLS
- Verify a published end-to-end runtime contract before depending on any remaining field
Limitations
- All current fields are validation and graph-revision metadata only
- A Ready status does not prove data-plane enforcement
- The current Operator intentionally drops the unconsumed runtime configuration
Security and operational guidance
- Treat accepted fields as desired-state metadata, not active enforcement
- Configure listener and upstream TLS through NexoDeploymentProfile
- Do not rely on authentication, tenant identity, limits, handshake, or pooling fields until an end-to-end runtime contract is published
Related steps
Release availability
- Current documentation: Unavailable at runtime: the current Operator validates and records NexoConnectionPipeline but does not deliver its settings to a runtime container.
See the component catalog for the complete comparison matrix.