Summary

The 2.x releases notes contains breaking changes: https://github.com/colinmarc/hdfs/releases/tag/v2.0.0

Message from the maintainers:

Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

When we install net-istio (and potentially other plugins) multiple validating webhooks are registered.

Unfortunately the webhooks are configured with just namespace selectors that are identical. Thus when config-istio is updated the serving webhook is invoked (which is a noop) and vice-versa for any serving config maps.

To avoid this we should use objectSelectors and distinctly label the

/kind feature

Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Add a sample of MMS using a custom model server similar to sklearn and triton that will reside [in

Problem

Sugar Controller is a separate install, which makes its functionality less useful.

Similar to knative/serving#11969, remove sugar-controller as a separate installable YAML, and integrate it into the main eventing controller. Use a namespace-level label selector to enable and disable the sugar controller at the namespace level.

The [current documenta

We are declaring certain specific configuration required for Kaniko directly in the IntegrationPlatformBuildSpec [1] and [2]. We should not let this details slip in the general configuration. A possible alternative is to provide a PublishStrategyOptions parameter with an open array/map of parameters that can be required by the strategy used (and where to move the aforementioned Kaniko para

Description
In the actual running of the function, we may need to control the concurrency of the function.

The current serving engines of OpenFunction - Knative Serving and Dapr - both have the ability to control runtime concurrency. We need to express this in the Function CRD in some concise and explicit way (annotations, properties, etc.)

Additional context
Reference:
https://kn

Currently, the source for Azure Service Bus Topics always manages its own Subscription to the selected Topic.

Similarly to the Google Pub/Sub source, we should allow users to manage the Subscription themselves if they prefer to, and simply give us the name of that Subscription so we can consume messages from it without reconciling it:

https://github.com/triggermesh/triggermesh/blob/c13be0932

The javadocs for the Java API are missing. The API methods reflect the same logic as in the Python API, such that much text can be borrowed from there.

Currently, ctriface/ doesn't pick up environment variables from the knative manifests. Firecracker-containerd supports it at a the container creation time as a runtime argument to the corresponding API call.

Example:

	container, err := o.client.NewContainer(
		ctx,
		vmID,
		containerd.WithSnapshotter(o.snapshotter),
		containerd.WithNewSnapshot(vmID, *vm.Image),
		containerd.With