Fluid Code Refactoring

[TrafalgarZZZ]

• [ ] Move common functions in DDC engines to a higher level abstraction like a common engine.
• [ ] Refactor runtimeInfo that make this concept more clear to developers, when to use runtimeInfo, what property should be put into runtimeInfo? Another confused concept would be base.RuntimeInterface, try to discriminate these two concepts.
• [x] Refactor pkg kubeclient.exec and make it reused by all runtimes #4270
• [x] Code deprecation for FUSE global mode. #4097
• [ ] Code deprecation for BitMap port allocator
• [ ] Code deprecation for CRD deprecated properties.
• [ ] Code deprecation for daemonset-like runtime workers.
• [ ] Code deprecation for some unused labels.
• [ ] Code deprecation for check deprecated PersistentVolume names.
• [x] Code cleaning: remove unused functions. #4063

BTW, is it possible to make integration with a new runtime's much easier with less coding? For example, runtime developers can forget about the lifecycles and simply implement the following components/functions:

• transform function and a runtime helm package: This is the core that Fluid sets up a runtime in the cluster.
• Functions that may interact with the runtime: For example, mounting/umounting functions, cache status report, health check.
• [Optional] Data operations like DataLoad, DataMigrate and DataProcess