ThinRuntime, as provided by Fluid, allows users to customize the storage system definition. In many scenarios, users build their own ThinRuntime images, so the configuration of imagePullSecrets is essential. This is because private images need to be pulled when the Fuse mountPod is started.

In this PR, we have added a multi-level definition of imagePullSecrets to the ThinRuntime and ThinRuntimeProfile custom resource definitions (CRDs).

Global level, under spec
Component level
a. Worker level, under spec.worker
b. Fuser level, under spec.fuse

When imagePullSecrets are defined in both the ThinRuntime and ThinRuntimeProfile CRs, the priority is as follows:

thinRuntime.spec.fuse.imagePullSecrets > thinRuntime.spec.imagePullSecrets > thinRuntimeProfile.spec.fuse.imagePullSecrets > thinRuntimeProfile.spec.imagePullSecrets

For example, secret-worker will be used in setup worker and secret-global will be used in setup fuse

apiVersion: data.fluid.io/v1alpha1
kind: ThinRuntime
metadata:
    name: demo
spec:
    imagePullSecrets: 
    - name: secret-global
    worker:
         imagePullSecrets: 
         - name: secret-worker
    fuse: