knative

Summary

Environment

• Latest argo-workflows from master installed from https://raw.githubusercontent.com/argoproj/argo-workflows/master/manifests/quick-start-postgres.yaml
• Kubernetes version: v1.22.2
• Minikube version: v1.23.2
• Mac OS X 11.6

Given the instructions defined here https://github.com/argoproj/argo-workflows/blob/master/docs/variables.md I expect that vari

/area API
/kind good-first-issue

Describe the feature

For flagged fields like kubernetes.podspec-fieldref the validation should include the name of the feature flag to toggle in the error message it surfaces. The validation logic is roughly here: https://github.com/knative/serving/blob/644798277d9fe6715e4f638281141356df46d7e1/pkg/apis/serving/k8s_validation.go#L246

To improve code quality we want to enforce failing build with linting issues

Acceptance:

• fix linting issues in Publisher Proxy / Eventing Controller, or mark individual issues with corresponding nolint comments
• enforce clean linting in the makefile. make release should fail if the linters find issues

/kind feature

Describe the solution you'd like

In pkg/apis/serving/v1beta1/inference_service_defaults.go the default InferenceService resource requests and limits are hard coded to be 1 cpu and 2Gi memory. These are reasonable defaults. However, the entire existence of these defaults should be disablable. Moreover, administrators should be able to quickly adjust defaults globally via t

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

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.

Seen in the logs of the controller today (formatted for readability):

{
  "level": "info",
  "ts": "2021-11-04T01:31:07.943Z",
  "logger": "triggermesh-controller",
  "caller": "tektontarget/reaper.go:90",
  "msg": "event sending results: {error 26 0  200: }",
  "commit": "b2dcbf2"
}

Notice how the following line prints the value returned by [zap.Error()](https://pkg.g

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