github.com/pachyderm/pachyderm@v1.13.4/doc/docs/archived/connecting_to_your_cluster.md (about)

     1  # Connecting to your Pachyderm Cluster
     2  
     3  
     4  ## Directly
     5  
     6  This is the recommended approach, especially if you're using the Pachyderm Dashboard or doing large uploads/downloads.
     7  
     8  ### Pachd
     9  
    10  To expose the pachd service, you need to change the k8s service:
    11  
    12  ```
    13  $ kubectl edit svc/pachd
    14  ```
    15  
    16  Then mark the `type` as `LoadBalancer`
    17  
    18  If you've gone to the trouble of [deploying within an existing VPC](./existing_vpc), you probably want to limit access to the cluster to IPs originating from this VPC.
    19  
    20  In this case, you want an internal load balancer. To expose the pachd service (for `pachctl` access), you'll need to also add the annotation:
    21  
    22  ```
    23  service.beta.kubernetes.io/aws-load-balancer-internal: '0.0.0.0/0'
    24  ```
    25  
    26  Once the load balancer is provisioned, you'll see the address that was provisioned via `kubectl get svc/pachd -o yaml`
    27  
    28  E.g. `internal-afsdfasdlkfjh34lkjh-3485763487.us-west-1.elb.amazonaws.com:650`
    29  
    30  Now set the pachd address of the associated context, so `pachctl` knows to directly connect:
    31  
    32  ```
    33  $ pachctl config update context `pachctl config get active-context` --pachd-address=internal-afsdfasdlkfjh34lkjh-3485763487.us-west-1.elb.amazonaws.com:650
    34  ```
    35  
    36  Finally, you can test that it's working by doing:
    37  
    38  ```
    39  
    40  $ pachctl version
    41  COMPONENT           VERSION                                          
    42  pachctl             1.7.3  
    43  pachd               1.7.3
    44  ```
    45  
    46  ### Dash
    47  
    48  Similar to exposing the pachd service above, you'll want to make the same modifications to the dash service:
    49  
    50  ```
    51  $ kubectl edit svc/dash
    52  ```
    53  
    54  The one additional configuration you'll need to add is the following annotation:
    55  
    56  ```
    57  service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout: "3600"
    58  ```
    59  
    60  (This is to allow the long lived websockets that the dash uses to stay alive through the load balancer)
    61  
    62  ## Port Forwarding
    63  
    64  Whenever you run a `pachctl` command and the pachd address config is not set, `pachctl` implicitly starts port forwarding to try to connect to your cluster. Port forwarding is the easiest way to poke around and verify your cluster is working, however, we don't recommend using it for production workloads, as it is rate limited to about 1MB/s.
    65  
    66  You can also explicitly start port forwarding via `pachctl port-forward`. This has the added bonus of port forwarding for Pachyderm Dashboard-related functionality. From there, you'll be able to access the Dashboard at `localhost:30080`.