Deployment Guide: On-Prem Deployment

The deployment process has no strict hardware or vendor-specific requirements. The only essential prerequisite is access to the Kubernetes API. Deployment is performed by applying standard Kubernetes manifest files to the target cluster.

This chapter outlines the necessary components, along with example manifest files and instructions for creating the required credentials secret if container images are hosted in a private registry.

List of Manifest Files:

•loadbalancer.yaml–defines the deployment of the Load Balancer component.

•scanner.yaml–deploys one or more Scanner instances.

•agents.yaml (optional)–launches a containerized Python Agent that can submit scan requests.

Scanner Agent that can be run in its own container

•containerregistry.yaml–configures access to a private container registry.

If container images are stored in a private repository, authentication credentials must be provided to pull the images from the repository. A Kubernetes ServiceAccount with an associated pull secret must be created to enable image retrieval.