Every kubeflow image should be scanned for security vulnerabilities.
It would be great to have a periodic security report.
Each of these images with vulnerability should be patched and updated.

Steps to reproduce

In Full Kubeflow mode, select a pipeline and click Create Run. During selecting experiment, open a dialog to select existing experiment.

By default, there is no available experiment, but there is no w

/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

Is your feature request related to a problem? Please describe.

As a user, I can attach comments to nodes that describe its purpose.

Elyra currently does not pass through this information to the target environment (Kubeflow Pipelines and Apache Airflow), even though it might

arena should support clean-task-policy "All" when training via tfjobs.
currently, only supports "Running"(clean RUNNING pod) or None(do nothing).
when job is done, often we need to remove ps, chief, evaluator and worker.

Summary

The current implementation does not allow creating templates specifying the parallelism field as per the Argo spec.

Use Cases

Many possible use cases, my current one is limiting the amount of parallel nodes running a certain template so as to save