[Features] support volume mount during lifeCycleAction

[loomts]

What is the user interaction of your feature Developer can customize volume mount during lifeCycleAction.

Is your feature request related to a problem? Please describe. etcd-addon need to check if tls enable in each lifeCycleAction, such as roleProbe and switchover, roleProbe action can attach target pod and use lorry container mount data and tls volumes, but switchover will startup a job pod which cannot mount exist volume right now.

Describe the solution you'd like Maybe we can adapt componentdefinition.yaml like this:

spec:
  lifecycleActions:
    switchover:
      withCandidate:
          container: xxx // method1: refactor each action and use the same volumeMount as the existing container
          targetVolumes: // method2: custom volume and volumeMount if exist (like backuppolicytemplate.yaml)
            volumes:
            - tls
            - data
            volumeMounts:
            - name: tls
              mountPath: {{ .Values.tlsMountPath }}
            - name: data
              mountPath: {{ .Values.dataMountPath }}
          exec:
            ...

[nayutah]

@leon-inf can kb agent solve such problem ?

[leon-inf]

It seems to be an implementation issue about some actions, they should follow the same behavior as role probes for example.

[nayutah]

It is good for supporting Action for uploading files, such as PostrgreSQL extension dynamic creation, and plugin creation for other databases.

[leon-inf]

@loomts The container field in Action has been supported by kb-agent, and the switchover action has been migrated to kb-agent too, you can try it again.