Storage quota on PVC

[cd1989]

/kind feature

In Cyclone, all Workflows share a common PVC, if some malicious Workflow try to fill up the PVC, all other Workflows would be affected. For example, write large amount of data to cache (such as CI/CD build speed up).

We should try to limit the storage that a Workflow, or a project can use. Similar to memory, CPU quota.

For cache, it's more friendly for Cyclone to limit in tenant level, so that no need to touch project concept in workflow engine.

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

[supereagle]

@cd1989 Is it done?

[cd1989]

Not yet. It's a totally different topic to what we have done.