Pachyderm Deployment Manifest¶
This section provides an overview of the Kubernetes manifest that you use to deploy your Pachyderm cluster. This section is provided for your reference and does not include configuration steps. If you are familiar with Kubernetes or do not have immediate questions about the configuration parameters, you can skip this section and proceed to Configuring Persistent Disk Parameters.
When you run the
pachctl deploy command, Pachyderm generates a JSON-encoded Kubernetes manifest which consists of sections that describe a Pachyderm deployment.
Pachyderm deploys the following sets of application components:
pachd: The main Pachyderm pod.
etcd: The administrative datastore for
dash: The web-based UI for Pachyderm Enterprise Edition.
pachctl deploy custom --persistent-disk <persistent disk backend> --object-store <object store backend> \ <persistent disk arg1> <persistent disk arg 2> \ <object store arg 1> <object store arg 2> <object store arg 3> <object store arg 4> \ [[--dynamic-etcd-nodes n] | [--static-etcd-volume <volume name>]] [optional flags]
As you can see in the example command above, you can run the
pachctl deploy custom command with different flags that generate an appropriate manifest for your infrastructure. The flags broadly fall into the following categories:
| ||Configures the storage resource for etcd. Pachyderm uses etcd |
to manage administrative metadata. User data is stored in an
object store, not in etcd.
| ||Configures the object store that Pachyderm uses for storing all |
user data that you want to be versioned and managed.
|Optional flags||Optional flags that are not required to deploy Pachyderm but |
enable you to configure access, output format, logging verbosity,
and other parameters.
Kubernetes Manifest Parameters¶
Your Kubernetes manifest includes sections that describe the configuration of your Pachyderm cluster.
The manifest includes the following sections:
Roles and permissions manifests
| ||Typically at the top of the manifest file Pachyderm produces, |
a roles and permissions manifest has the
to applications in a lightweight way. Pachyderm's
service account is called
| ||Depending on whether you used the |
the next manifest kind is Role or ClusterRole.
| ||This manifest binds the |
| ||If you used |
value that you specify for
a manifest for creating a
enterprises is an NFS mount backed by a storage fabric. In this case, a
with your Kubernetes administrators to learn what resources are available
for your deployment.
| ||If you deployed Pachyderm by using |
See this manifest's name in the Deployment manifest
| ||If you used the |
this manifest specifies the kind of storage and provisioner that
is appropriate for what you have specified in the
Note: You will not see this manifest if you specified
| ||In a typical Pachyderm deployment, you see three |
If you use
Pachyderm does not create a
the manifests for the Pachyderm enterprise UI only. The most common items
that you can edit in
various services, and the
To make your
add environment variables to a
You can see how what environment variables to add in the OpenShift example.
Pachyderm pods manifests
| ||Declares the desired state of application pods to Kubernetes. If you |
configure a static deployment, Pachyderm deploys
Pachyderm deploys the
flag, Pachyderm omits the deployment of the
| ||For a |
manifest with a
Pachyderm Kubernetes secrets manifests
| ||Pachyderm uses the Kubernetes |
are necessary to access object storage. The final manifest uses the
command-line arguments that you submit to the
command to store such parameters as region, secret, token, and endpoint, that are
used to access an object store. The exact values in the secret
depend on the kind of object store you configure for your deployment. You
can update the values after the deployment either by using
to deploy a new