You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Submission client redesign to use a step-based builder pattern.
This change overhauls the underlying architecture of the submission
client, but it is intended to entirely preserve existing behavior of
Spark applications. Therefore users will find this to be an invisible
change.
The philosophy behind this design is to reconsider the breakdown of the
submission process. It operates off the abstraction of "submission
steps", which are transformation functions that take the previous state
of the driver and return the new state of the driver. The driver's state
includes its Spark configurations and the Kubernetes resources that will
be used to deploy it.
Such a refactor moves away from a features-first API design, which
considers different containers to serve a set of features. The previous
design, for example, had a container files resolver API object that
returned different resolutions of the dependencies added by the user.
However, it was up to the main Client to know how to intelligently
invoke all of those APIs. Therefore the API surface area of the file
resolver became untenably large and it was not intuitive of how it was
to be used or extended.
This design changes the encapsulation layout; every module is now
responsible for changing the driver specification directly. An
orchestrator builds the correct chain of steps and hands it to the
client, which then calls it verbatim. The main client then makes any
final modifications that put the different pieces of the driver
together, particularly to attach the driver container itself to the pod
and to apply the Spark configuration as command-line arguments.
* Add a unit test for BaseSubmissionStep.
* Add unit test for kubernetes credentials mounting.
* Add unit test for InitContainerBootstrapStep.
* unit tests for initContainer
* Add a unit test for DependencyResolutionStep.
* further modifications to InitContainer unit tests
* Use of resolver in PythonStep and unit tests for PythonStep
* refactoring of init unit tests and pythonstep resolver logic
* Add unit test for KubernetesSubmissionStepsOrchestrator.
* refactoring and addition of secret trustStore+Cert checks in a SubmissionStepSuite
* added SparkPodInitContainerBootstrapSuite
* Added InitContainerResourceStagingServerSecretPluginSuite
* style in Unit tests
* extremely minor style fix in variable naming
* Address comments.
* Rename class for consistency.
* Attempt to make spacing consistent.
Multi-line methods should have four-space indentation for arguments that
aren't on the same line as the method call itself... but this is
difficult to do consistently given how IDEs handle Scala multi-line indentation
in most cases.
Copy file name to clipboardexpand all lines: resource-managers/kubernetes/core/src/main/scala/org/apache/spark/deploy/kubernetes/InitContainerResourceStagingServerSecretPlugin.scala
Copy file name to clipboardexpand all lines: resource-managers/kubernetes/core/src/main/scala/org/apache/spark/deploy/kubernetes/SparkPodInitContainerBootstrap.scala
0 commit comments