Configure the dynamic plugins cache
The dynamic plugins cache reduces platform boot time by storing already-installed plugins and skipping redundant downloads when the configuration does not change.
When you enable dynamic plugins cache:
- The system calculates a checksum of each plugin’s YAML configuration (excluding
pluginConfig). - The system stores the checksum in a file named
dynamic-plugin-config.hashwithin the plugin’s directory. - During boot, if a plugin’s package reference matches the earlier installation and the checksum does not change, the system skips the download.
- The system automatically removes plugins that you disabled since the earlier boot.
dynamic-plugins-root must be a persistent volume.Create a persistent volume claim Copy linkLink copied!
Store already-installed dynamic plugins on a persistent volume to reduce Red Hat Developer Hub boot time and avoid redundant downloads.
The dynamic plugins cache reduces platform boot time by storing already-installed plugins and skipping redundant downloads when the configuration does not change.
When you enable the dynamic plugins cache:
- The system calculates a checksum of each plugin's YAML configuration, excluding
pluginConfig. - The system stores the checksum in a file named dynamic-plugin-config.hash within the plugin's directory.
- During boot, if a plugin's package reference matches the earlier installation and the checksum has not changed, the system skips the download.
- The system automatically removes plugins that you disabled since the earlier boot.
Create PVC with Operator Copy linkLink copied!
Create a persistent volume claim for the dynamic plugin cache in Operator deployments by replacing the default dynamic-plugins-root volume.
Before you begin Copy linkLink copied!
- You have installed Red Hat Developer Hub on OpenShift Container Platform using the Red Hat Developer Hub Operator.
- You have installed the OpenShift CLI (
oc).
Procedure Copy linkLink copied!
Create PVC with Helm Chart Copy linkLink copied!
Create a persistent volume claim for the dynamic plugin cache in Helm deployments to persist the cache across pod restarts.
Before you begin Copy linkLink copied!
- You have installed Red Hat Developer Hub using the Helm chart.
- You have installed the OpenShift CLI (
oc).
Procedure Copy linkLink copied!
Resolve plugin configuration errors Copy linkLink copied!
Fix temporary 404 errors caused by inconsistent dynamic plugins cache states across Red Hat Developer Hub replicas.
Before you begin Copy linkLink copied!
Your API version is v1alpha5 or later.
About this task Copy linkLink copied!
When multiple Red Hat Developer Hub replicas share a single dynamic plugins cache persistent volume claim (PVC), updating the configuration through the Operator can trigger temporary 404 errors. This happens because replicas can read inconsistent cache states before all replicas finish synchronizing. Using an individual cache per pod resolves this issue.
Procedure Copy linkLink copied!
Set dynamic plugin cache pull policy Copy linkLink copied!
Set the pull policy and download parameters for the dynamic plugins cache in the dynamic-plugins.yaml file.
Procedure Copy linkLink copied!
pullPolicy: IfNotPresent(default)- Downloads the artifact only if it is not already present in the dynamic-plugins-root folder, without checking image digests.
pullPolicy: Always- Compares the image digest in the remote registry and downloads the artifact if it has changed, even if Red Hat Developer Hub already downloaded the plugin. When applied to the NPM download method, downloads the remote artifact without a digest check.
forceDownload: false(default)- Older option that downloads the artifact only if it is not already present in the dynamic-plugins-root folder, without checking image digests.
forceDownload: true- Older option that forces a reinstall of the plugin, bypassing the cache.
Example configuration to download a remote artifact without a digest check, using pullPolicy: Always:
plugins:
- disabled: false
pullPolicy: Always
package: 'oci://quay.io/example-org/example-plugin:v1.0.0'
pullPolicy takes precedence over forceDownload. The forceDownload option may become deprecated in a future Red Hat Developer Hub release.