Experimental features

    In order to achieve that goal in Knative Eventing, we have a process to include new features. This allows users like you to try out new features and provide feedback back to the project.

    This document explains how to enable experimental features and which ones are available today.

    For more details about the process, the feature phases, quality requirements and guarantees, check out the Experimental features process documentation.

    Warning

    Depending on the feature stage, an experimental feature might be unstable and break your Knative setup or even your cluster setup, use them with caution. For more details about quality guarantees, check out the .

    You must have a Knative cluster running with the Eventing component installed. Learn more

    When installing Eventing, the ConfigMap is added to your cluster in the knative-eventing namespace. In order to enable a feature, you just need to add it to the config map and set its value to enabled. For example, to enable new-cool-feature:

    Flag name: kreference-group

    Stage: Alpha, disabled by default

    Tracking issue:

    When using the type to refer to another Knative resource, you can just specify the API group of the resource, instead of the full APIVersion.

    For example, in order to refer to an InMemoryChannel, instead of the following spec:

    You can use the following:

    With this feature you can allow Knative to resolve the full APIVersion and further upgrades, deprecations and removals of the referred CRD without affecting existing resources.

    At the moment this feature is implemented only for Subscription.Spec.Subscriber.Ref and .

    DeliverySpec.Timeout field

    Flag name: delivery-timeout

    Stage: Alpha, disabled by default

    Tracking issue:

    When using the delivery spec to configure event delivery parameters, you can use timeout field to specify the timeout for each sent HTTP request. The duration of the timeout parameter is specified using the ISO 8601 format.

    The following example shows a Subscription that retries sending an event 3 times, and on each retry the request timeout is going to be 5 seconds:

    You can specify a delivery spec for Channels, Subscriptions, Brokers, Triggers, and any other resource spec that accepts the field.