Enterprise-grade HAProxy load balancer container with FIPS 140-2 compliance, providing secure and high-performance load balancing, SSL/TLS termination, and traffic routing capabilities for mission-critical applications. Features STIG hardening and security optimizations for regulated environments.
Core capabilities and strengths of this container
Typical scenarios where this container excels
Download the container image from the registry
docker pull clnstrt-images.cleanstart.com/$ORGANIZATION/haproxy-fips:latestdocker pull clnstrt-images.cleanstart.com/$ORGANIZATION/haproxy-fips:latest-devRun the container with basic configuration
docker run -it --name haproxy-fips-test clnstrt-images.cleanstart.com/$ORGANIZATION/haproxy-fips:latest-devDeploy with production security settings
docker run -d --name haproxy-fips-prod \
--read-only \
--security-opt=no-new-privileges \
--user 1000:1000 \
-v /etc/haproxy:/etc/haproxy:ro \
-p 443:443 \
clnstrt-images.cleanstart.com/$ORGANIZATION/haproxy-fips:latestMount local directory for persistent data
docker run -v $(pwd)/haproxy.cfg:/etc/haproxy/haproxy.cfg:ro clnstrt-images.cleanstart.com/$ORGANIZATION/haproxy-fips:latestRun with custom port mappings
docker run -p 80:80 -p 443:443 -p 8404:8404 clnstrt-images.cleanstart.com/$ORGANIZATION/haproxy-fips:latestConfiguration options available through environment variables
/etc/haproxy/haproxy.cfghaproxy8404/etc/ssl/certsRecommended security configurations and practices
Recommended security context for Kubernetes deployments
securityContext:
runAsNonRoot: true
runAsUser: 1000
runAsGroup: 1000
readOnlyRootFilesystem: true
allowPrivilegeEscalation: false
capabilities:
drop: ["ALL"]
add: ["NET_BIND_SERVICE"]Essential links and resources for further information