knative

Summary

From an archived workflow, click on "Resubmit" in the UI

The created workflow do not have the appropriate labels

/!\ the bug happens only for archived workflows (when you resubmit a "normal" workflow, the labels are kept)

Be cautious, some labels should not be copied (like workflows.argoproj.io or workflows.argoproj.io/phase)

however, the labels placed manually by the us

/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

ORY, as in the name of the stack, should be spelled with all capital letters.
This spelling in our documentation is not consistent in that regard and sometimes the incorrect Ory spelling is used. For example, see this document.
This should be corrected.

Area

• Documentation

**Reaso

/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

Happened quite some times with 1.5. There's a KameletBinding called timer-source-to-mysql-sink. It's deleted but then the CLI tries to remove the integration (it should not, it's automatically cleaned up).

[nferraro@localhost kamelet-catalog]$ kamel reset
1 kamelet bindings deleted from namespace camel
could not delete integration timer-source-to-mysql-sink from namespace camel: integr

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.
Whenever a new tagged release is created, we want to run the mike versioning CI so that iter8.tools documentation is auto-updated.

Describe the feature/solution you'd like
Make the mike versioning workflow trigger on releases (not just manual). Additionally, extract major and minor version numbers f

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