Lightup Hybrid

If you prefer to host Lightup in your own environment, Lightup Hybrid can be deployed to a dedicated VM or to an existing Kubernetes cluster (self-managed or cloud-managed).

Lightup Hybrid deployment keeps all data-oriented processes, such as metric collection, monitor training, integrations, and alerting, within your environment.

This page provides prerequisites to help you prepare for Lightup deployment. Please contact Lightup Support to arrange for actual deployment.


Outbound connectivity

Your system instance must always have access to the following internet services for the proper functioning of Lightup. You should modify your firewall rules if you cannot access any of these services.

ServiceDomains to whitelist
Linux package repositories (apt/yum repositories): For support packages needed on the VM host environment.One of the following, depending on which Linux version you install:
- * (yum/dnf Repositories— enables RHEL/Fedora System Update Packages)
- * (apt Repositories— enables Ubuntu System Update Packages)
Replicated ( Lightup application software is packaged and licensed using Replicated. The application bundle (Kubernetes binaries, Docker containers, license file) are pulled from Replicated during the installation sequence and subsequent upgrades.- * (enables Upstream Docker images via The on-prem docker client uses a license ID to authenticate to This domain is owned by Replicated, Inc., headquartered in Los Angeles, CA.)
- (source of replicated images for releases)
- * (source of replicated images for releases)
- * (source of replicated images for releases)
- (source of Kubernetes cluster installation scripts and artifacts: an application identifier is sent in a URL path, and bash scripts and binary executables are served from This domain is owned by Replicated, Inc., headquartered in Los Angeles, CA)
- (source of tar.gz: packages are downloaded from Amazon S3. The IP ranges to whitelist for accessing these can be scraped dynamically from the AWS IP Address Ranges documentation.)
Datadog: Lightup uses Datadog for container logging, metric monitoring and Kubernetes pod health monitoring* (enables Lightup monitoring)
Lightup AWS Services: Lightup leverages a dedicated single-tenant service for install and upgrade requirements.* (enables Lightup system updates and calls)

Deployment environment

Deployment targetSupported versionsMinimum hardware resources
New Linux VMUbuntu 20.04 or RHEL88 vCPUs, 64GB RAM, and 200GB of persistent, flat, unpartitioned hard disk capacity (EBS or similar)
Existing k8s clusterKubernetes 1.24 through 1.27Each node: 4 vCPUs / 32 GB RAM
Whole cluster: 8 vCPUs / 64GB RAM

Cloud-Managed Kubernetes (EKS, AKS, GKE)

If you’re using AWS EKS for your Kubernetes cluster, make sure that the following add-ons or equivalent have been installed:

Custom Lightup Access Point

Lightup exposes a NodePort on port 30443 that you can use to access the Lightup UI.

If the nodes in your kubernetes cluster have public IP addresses, then you can access the UI at https\://<ip-address-or-host-name-of-your-VM>:30443. If the nodes do not have a public IP address or if you want to configure a URL, you can use a Load Balancer to access the UI. Lightup only works with supported domains, so you'll need to provide Lightup support with your IP address / hostname / URL.

The following example shows how you'd access the Lightup UI at using a Network Load Balancer in AWS:

  1. Create a certificate for with AWS Certificate Manager (ACM).

  2. Verify the certificate with the option to create records in Route 53.

  3. Copy the certificate ARN— you'll need this for the following step.

  4. Update the following manifest for the Kubernetes service that will generate the NLB, and save it as a file named lightup-nlb-service.yaml:

     apiVersion: v1  
       kind: Service  
         name: lightup-backend  
           app: backend  
         externalTrafficPolicy: Local  
       - name: backend  
          port: 443  
          protocol: TCP  
          targetPort: 8000  
        app: backend  
        release: backend  
      type: LoadBalancer
  5. Deploy the NLB using kubectl and the YAML file you saved:
    kubectl apply -n lightup -f lightup-nlb-service.yaml

  6. Copy the generated NLB's URL.

  7. Create a new Route 53 A record for to route to the NLB's URL.