LATEST VERSION: v1.1 - RELEASE NOTES
Pivotal Container Service v1.0

Load Balancers in PKS

Page last updated:

This topic describes the types of load balancers that are used in Pivotal Container Service (PKS).

You can configure load balancers for the following:

  • PKS API: Configuring this load balancer allows you to run PKS Command Line Interface (CLI) commands from your local workstation.
  • Kubernetes Clusters: Configuring a load balancer for each new cluster allows you to run Kubernetes CLI (kubectl) commands on the cluster.
  • Workloads: Configuring a load balancer for your application workloads allows external access to the services that run on your cluster.

The following diagram shows where each of the above load balancers can be used within your PKS deployment:

PKS diagram including all load balancer options

If you use either vSphere with NSX-T or GCP, you can create load balancers within your cloud provider console.

If your cloud provider does not offer load balancing, you can use any external TCP or HTTPS load balancer of your choice.

About the PKS API Load Balancer

The load balancer for the PKS API allows you to access the PKS API from outside the network. For example, configuring a load balancer for the PKS API allows you to run PKS CLI commands from your local workstation.

For information about configuring the PKS API load balancer, see the Configure External Load Balancer section of Installing and Configuring PKS.

About Kubernetes Cluster Load Balancers

When you create a cluster, you must configure external access to the cluster by creating an external TCP or HTTPS load balancer. The load balancer allows the Kubernetes CLI to communicate with the cluster.

If you create a cluster in a non-production environment, you can choose not to use a load balancer. To allow kubectl to access the cluster without a load balancer, you can do one of the following:

  • Create a DNS entry that points to the cluster’s master VM. For example:
    my-cluster.example.com    A    10.0.0.5
  • On the workstation where you run kubectl commands, add the master IP address of your cluster and kubo.internal to the /etc/hosts file. For example:
    10.0.0.5 kubo.internal

For information about configuring a cluster load balancer, see Create a Cluster.

About Workload Load Balancers

To allow external access to your app, you can either create a load balancer or expose a static port on your workload.

For information about configuring a load balancer for your app workload, see Deploy and Access Basic Workloads.


Please send any feedback you have to pks-feedback@pivotal.io.

Create a pull request or raise an issue on the source for this page in GitHub