Closed cdrage closed 6 years ago
ping @pradeepto @kadel
so above you can see that we have DeploymentSpec, but PodSpec is already coming from ControllerFields
, see below:
Similarly we have done for all controllers, so is Job controller is implemented:
Should we indicate in the documentation that depending on what controller is defined, it changes what you can define in the Kedge file?
This is true, PodSpec is always constant, but depending on the controllerTypeSpec things will change.
@surajssd explained pretty well.
Essentially, Kedge spec == ControllerFields (contains PodSpec) + ControllerSpec (job controller contains parallelism field).
@containscafeine Thanks :) Yeah, that's what I thought. So essentially it's a combination of both PodSpec + ControllerSpec in the "root" of the Kedge file. For example, ContainerSpec is within containers
key, ConfigMapSpec within configmaps
key, etc.
Let's keep this issue open so we can track regarding adding extra documentation to clarify all of this :+1:
PR #492
Yup :+1:
So...
Within our documentation we've said that the "Kedge" file "extends" PodSpec.
Yet for example:
We use "Parallelism" which is considered part of the JobSpec, not PodSpec.
Should we indicate in the documentation that depending on what controller is defined, it changes what you can define in the Kedge file?
Instead of saying that the Kedge file is simply an extension of PodSpec..