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:Documentation Index
Fetch the complete documentation index at: https://docs.endorlabs.com/llms.txt
Use this file to discover all available pages before exploring further.
- Azure Kubernetes Service (AKS)
- Google Kubernetes Engine (GKE)
- Amazon Elastic Kubernetes Service (EKS)
- Self-hosted Kubernetes clusters
Kubernetes cluster requirements for Outpost
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. The total scans per node per day (24 hours) is calculated based on the following formula.Storage requirements for Outpost
Storage requirements for Outpost depend on the number of projects that you want to scan and the size of the repositories. Storage requirements increase in direct proportion to the number of concurrent scans. You can use the following formula to calculate the storage requirements if you are runningN number of concurrent scans.
- Project sizes: 10 GB, 8 GB, 6 GB, 4 GB, 2 GB
- Concurrent scans: 3
- Storage calculation: 10 GB + 8 GB + 6 GB + extra space
- Total storage required: 24 GB + extra space for other files
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.