Skip to main content
Version: 3.1

Set up Access for Portworx Backup Web Console

Applicable to both Classic and Federated modes

Before you expose the Portworx Backup web console, decide how much network access it needs. For most deployments, keep the console private and reachable only through a controlled path:

  • kubectl port-forward to the px-backup-ui service (no external endpoint)
  • A private or internal ingress
  • A VPN or bastion host
  • A private (internal) load balancer, using your cloud provider's internal load balancer annotation

Setting the UI service type to ClusterIP, or keeping LoadBalancer with an internal load balancer annotation, prevents the console from being reachable on a public, internet-facing endpoint. For the service types, per-cloud annotations, and source-range options, see Configure Access to Portworx Backup Web Console.

caution

On managed cloud platforms, a LoadBalancer service can create a public, internet-facing endpoint unless you request an internal load balancer. Expose the console publicly only when you specifically intend to.

If the standard Portworx Backup web console endpoint configuration does not meet your requirements, you can configure access using HTTPS, access it through the load balancer (ingress, AWS ALB), or navigate to one of your node IPs directly.

Last updated on