knative

/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

Description

The Eventing controllers (eventing-controller-nats and eventing-controller), are creating NATS Subjects and Webhooks (respectively) with clean names (more info: kyma-project/kyma#10218).

Subscription

apiVersion: eventing.kyma-project.io/v1alpha1
kind: Subscription
metadata:
  name: somename
  namespace: somenamespace
spec:
  f

/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.

Is your feature request related to a problem? Please describe the problem.
At times, we merge code to main only to have the build-and-push workflow fail because of a problem with docker build

Describe the feature/solution you'd like
Include a test of the docker build of image in the build-and-test workflow

**Will this feature/solution bring new benefits for Iter8 developers

The test does not gracefully remove the minio server. Once it is added, it should be re-enabled.