knative

Checklist

• Double-checked my configuration.
• Tested using the latest version.
• Used the Emissary executor.

Summary

Providing a lengthy argument to a container template, or a lengthy source to a script template, causes the provided argument/source to visually overflow in the UI.

I have observed this issue in multip

/area API
/area autoscale
/kind cleanup

Actual Behavior

The max-scale and min-scale annotation has been introduced in knative/serving#12103 alignment. The client was using those names, but recently this changed to the inverse - knative/client#958. This leads to confusion on docs, and UX as seen in: https://github.com/knative/docs/iss

/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

I'm getting this warning on k8s 1.23:

Warning: policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget

on

Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.0", GitCommit:"c2b5237ccd9c0f1d600d3072634ca66cefdf272f", GitTreeState:"clean", BuildDate:"2021-08-04T18:03:20Z", GoVersion:"go1.1

We don't have a direct way to fill the platform.Spec.Build.PublishStrategyOptions. It would be nice to include it in the kamel install as an option.

We should also transform the kaniko-build-cache option to fit into the new model.

Originally posted by @squakez in apache/camel-k#1238 (comment)

Description
https://openfunction.dev/docs/user-guide/use-events/use-event-bus-and-trigger/#create-an-eventbus-and-an-eventsource
Using EventBus to build EventSource according to the official documentation causes openfunction-controller-manager to exit with an exception.

Environmental
+------------------+---------+
| COMPONENT | VERSION |
+------------------+---------+
| Ope

Currently, TriggerMesh has a webhook component up and running but it does almost nothing.
We need to start implementing validation and [defaulting](https://github.com/triggermesh/triggermesh/b

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