Look up details

Find resource schemas, configuration identifiers, metrics, and implementation constraints. This index points to the existing sources of technical detail rather than repeating their values. Some settings pages also include configuration procedures; use the linked page for its exact scope and requirements.

Serving

• Serving API: resource fields and types.
• Deployment-to-Service mapping: illustrative manifest correspondence and workload-fit constraints, not a migration or endpoint-cutover procedure.
• Concurrency settings and scale bounds: autoscaling annotations and cluster-level settings.
• Default configuration and deployment resources: platform configuration keys.
• Serving metrics and feature flags.

The autoscaling overview links to further settings for metrics, targets, and scale-to-zero.

Eventing

• Eventing API: resource fields and types.
• Trigger filtering and annotations reference: filter dialects, compatibility, field precedence, and annotations.
• Event delivery reference: retry, backoff, dead-letter destinations, failure extensions, and implementation support. Consult its validation warnings before depending on unresolved implementation behavior.
• Source configuration: ApiServerSource, PingSource, ContainerSource, and SinkBinding.
• Eventing metrics and feature configuration.
• Security configuration details: transport encryption modes and authorization policies and modes. These pages also contain procedures. Check their feature prerequisites and implementation compatibility; this index does not promise universal support.

For other integrations, start with the source catalog or sink catalog, then consult the relevant implementation's documentation. Support is not uniform across implementations.

Functions and command-line tools

• kn command reference: upstream CLI command documentation.
• func command reference: upstream Functions command documentation.

These links use the documentation release branch when configured; otherwise they fall back to upstream main. That fallback is not a guarantee that the reference matches your installed binary. Use reference matching your installed kn or func version when checking available commands and flags.

Use the CLI overview for tool roles and connection options. The upstream documentation is authoritative for command details; this index does not maintain a second command catalog.

Installation and cluster configuration

• Installation requirements: capacity recommendations, administrator prerequisites, and release-compatibility destinations.
• Installation extensions catalog: networking, messaging, and integration options with implementation-specific destinations.
• Operator configuration field map: ConfigMap mapping and destinations for documented custom resource fields. It is an entry reference, not a complete generated Operator API schema.
• Operator-supported component versions: bundled Serving/Eventing releases, distinct from Kubernetes compatibility.
• Installation artifacts: Serving files and Eventing files.
• Administrator configuration overview: links to the ConfigMaps and settings for each component.

Use the matching version

Use documentation that matches your installed Knative release. The Serving and Eventing API pages are populated from generated reference during the release build; their source placeholders are not the full published API documentation. Command-documentation links above use the site's version-aware link macros.

To change a setting, find a how-to guide. To understand the behavior behind it, read explanation.