Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.3.0
-
None
Description
The appId now can be only access in KuberntesDriverConf and KubernetesExecutorConf, but can't be accesss in KubernetesConf.
Some user featurestep are using KubernetesConf as init constructor parameter in order to share the featurestep between driver and executor. So, we'd better add appId to KubernetesConf to help such featurestep access appId.