This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Outpost requirements

Learn about the requirements for Outpost.

You need a Kubernetes cluster with nodes that have at least 8 cores and 32 GB of RAM. Nodes should be running Linux.

You must create a namespace in your Kubernetes cluster to deploy Outpost. Use this namespace when you configure Outpost integration in Endor Labs.

Outpost currently supports the following Kubernetes distributions:

  • Azure Kubernetes Service (AKS)
  • Google Kubernetes Engine (GKE)
  • Amazon Elastic Kubernetes Service (EKS)
  • Self-hosted Kubernetes clusters

The total number of nodes in the cluster depends on the number of projects that you want to scan and the number of scans that you want to run in a day. On average, each scan is expected to take approximately one hour to complete.

The total scans per node per day (24 hours) is calculated based on the following formula.


Total scans per node per day = (CPU cores in the node ÷ 8) × 24

You can use the following formula to calculate the number of nodes required.


Number of nodes = Total projects ÷ Total scans per node per day

The following table shows the number of nodes required for different combinations of projects and scans.

Number of projects Node specification Scans per node per day Number of nodes
48 8 cores, 32 GB RAM 24 2
1000 8 cores, 32 GB RAM 24 42
1000 32 cores, 128 GB RAM 96 11

Network requirements for Outpost

Ensure the following network requirements are met for Outpost:

  • Egress Access: Required. Allow outbound traffic to Endor Labs platform, toolchains, and package managers.
  • DNS Resolution: Required. Allow list of necessary domains.
  • Network Policies: Required. Allow outbound traffic to Endor Labs platform, toolchains, and package managers.