NetBox Enterprise Helm Installation Guide
Beta Notice: These Helm charts are currently in beta. While stable for testing and development environments, please thoroughly test in your specific environment before production deployment. For the most up-to-date information, please refer to the main documentation.
Overview
NetBox Enterprise is a comprehensive network source of truth and infrastructure resource management platform. This guide covers the production deployment of NetBox Enterprise using Helm on Kubernetes.
Architecture
The NetBox Enterprise Helm chart deploys:
Core Components
- NetBox Enterprise Web: Main application pods running Nginx Unit as the application server
- NetBox Enterprise Worker: Background task processing pods (RQ workers)
- Enterprise Licensing: Integrated licensing and telemetry components
Data Layer
- PostgreSQL: Primary database (internal via Crunchy Data Operator or external)
- Redis: Task queue and caching (internal via Bitnami chart)
- Persistent Storage: Media files, reports, and custom scripts
Optional Components
- Reloader: Automatic pod restarts on configuration changes
Security Features
- Non-root containers with read-only root filesystem
- Pod security contexts with seccomp profiles
- TLS support for all external connections
- Network policy support
This installation guide covers both internal database deployments (default) and external database configurations for production environments.
Authentication and Access
NetBox Enterprise requires authentication to access both the container registry and Helm charts. This documentation uses the LICENSE_ID method as the standard authentication approach:
- Registry Access: Uses
proxy.enterprise.netboxlabs.comfor Docker images - Helm Charts: Uses
registry.enterprise.netboxlabs.comfor Helm chart access - Authentication: Your LICENSE_ID serves as both username and password for registry access
Documentation Approach
The commands in this guide use variables for flexibility:
$LICENSE_ID- Your NetBox Enterprise license identifier$USERNAME- Your email address (for registry login)$CHART_VERSION- Helm chart version (set to use specific version or leave empty for latest)
This allows you to customize versions and credentials while following the same procedures across different environments.
Next Steps
Continue with the installation process:
- Prerequisites - System requirements and setup
- Installation - Recommended guided installation
- Operations - Backup, upgrade, and scaling procedures
- Troubleshooting - Common issues and solutions
Complete Installation Guide
- → Overview - Architecture and approach
- Prerequisites - System requirements
- Installation - Installation procedures
- Values Guide - Configuration reference
- Operations - Backup and maintenance
- Troubleshooting - Problem resolution