knative

https://oss-fuzz.com/testcase-detail/5254033034575872

panic: runtime error: index out of range [2] with length 2
--
  |  
  | goroutine 17 [running, locked to thread]:
  | github.com/argoproj/argo-workflows/v3/server/artifacts.(*ArtifactServer).getArtifact(0x10c0002b9428, {0x2b322c0, 0x10c0002c1760}, 0x10c0003abd00, 0x0)
  | github.com/argoproj/argo-workflows/v3/server/artifacts/a

Describe the feature

Cur

/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

The operator prints periodically this info:

{"level":"info","ts":1623416979.434832,"logger":"camel-k","msg":"could not find any knative type in namespace camel, last error was: services.serving.knative.dev is forbidden: User \"system:serviceaccount:camel:camel-k-operator\" cannot list resource \"services\" in API group \"serving.knative.dev\" in the namespace \"camel\""}

It looks l

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

I have faced an error with yq latest binary version "v4.6.3" yq_linux_amd64, https://github.com/mikefarah/yq/releases/tag/v4.6.3, in my Debian.

Error: unknown command "read" for "yq"

The command for this version is:

export SVC_URL=kubectl get rt greeter -o yaml | yq eval '.status.url' - &&
http $SVC_URL

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