A build pipeline needs reliable access to the packages it downloads and the artifacts it publishes. Artifactory HA runs multiple Artifactory repository servers together so one server does not have to handle every request or be the only access point. It suits teams whose builds and releases depend on a shared package service. Keeping that service available also requires resilient database and file storage, not merely extra application replicas.
Deployment and operating notes
The recovered link points at the archived community chart repository. JFrog publishes an Artifactory HA chart in its own chart repository, with an HA license requirement and external PostgreSQL recommended for production. The current chart documentation also notes that newer Artifactory nodes can all perform cluster tasks, so the historical explanation of a single special primary node should not guide a new topology.
High availability depends on the database, binary storage, load balancer and failure domains as well as the number of Artifactory pods. Record the existing chart and application versions, master and join keys, database credentials, filestore configuration and ingress behavior before migration. Follow the vendor-supported application upgrade path and chart image-migration notices. Back up the database and binary data as a coordinated set and rehearse a restore; scaling replicas does not create that safety net. Validate artifact checksums, repository permissions and build-tool authentication after cutover. Keep licensing and support entitlements in the decision rather than assuming the old chart’s defaults remain available.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub confirms that helm/charts is archived: this is a historical chart distribution, not evidence that the application itself is retired. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
Artifactory supports a High Availability network configuration with a cluster of 2 or more, active/active, read/write Artifactory servers on the same Local Area Network (LAN).
Setting up several servers in an HA configuration is supported with an Enterprise License and presents several benefits to your organization.
Maximize Uptime
Artifactory HA redundant network architecture means that there is no single-point-of-failure, and your system can continue to operate as long as at least one of the Artifactory nodes is operational. This maximizes your uptime and can take it to levels of up to “five nines” availability.
Manage Heavy Loads
By using a redundant array of Artifactory server nodes in the network, your system can accommodate larger load bursts with no compromise to performance. With horizontal server scalability, you can easily increase your capacity to meet any load requirements as your organization grows.
Minimize Maintenance Downtime
By using an architecture with multiple Artifactory servers, Artifactory HA lets you perform most maintenance tasks with no system downtime.
Architecture
Artifactory HA architecture presents a Load Balancer connected to a cluster of two or more Artifactory servers that share a common database where all the Artifactory configuration files are maintained. Binaries may be stored on a Network File System, or using a zoned sharded binary provider as described in Configuring Sharding for High Availability.
The Artifactory cluster nodes must be connected through a fast internal LAN in order to support high system performance as well as to stay synchronized and notify each other of actions performed in the system instantaneously. One of the Artifactory cluster nodes is configured to be a “primary” node. Its roles are to execute cluster-wide tasks such as cleaning up unreferenced binaries.
Sources & further reading
Spotted something that needs another look?
Help improve this page →