ESET PRIVATE Scanning Solutions – Table of Contents

Prerequisites

Container Registry Access

ESET provides an account enabling direct installation of the ESET PRIVATE Scanning Solution Helm chart into the target environment. For air-gapped environments or those using a local image registry, both the Helm chart and container images can be downloaded for local availability.

ESET Container registry: ecscnprod.azurecr.io

Deployment Prerequisites

The following components and CLI utilities are required to deploy the solution. Ensure the specified minimum versions are met before proceeding.

Tool

Purpose

Minimum Version

Kubernetes

Container orchestration platform

1.34

Helm

Package management for Kubernetes

3.17.2

kubectl

Kubernetes Cluster interaction

1.34

Supported Integrations

The following optional components are not required for baseline deployment but may be enabled to extend the solution's security, observability, and scaling capabilities. If used, the versions listed below are recommended to ensure compatibility.

Service

Description

Minimum Version

Valkey Operator

Redis-compatible in-memory data store operator

0.0.61

Cert-Manager

Kubernetes certificate management controller

1.19

Prometheus-Operator

Monitoring (at least stripped CRDs are required)

0.88.0

LoadBalancer

Cloud provider load balancer integration

N/A

Cilium

CNI required for CiliumNetworkPolicies

1.18.5

Gateway API

Gateway API CRDs

1.4

Traefik

Gateway API implementation

39.0.0

External Secrets Operator

Only if ExternalSecrets are used

1.2.1