feat: add pluginImageRegistry and pluginImageNamespace config for built-in plugins#666
Merged
johnlanni merged 1 commit intohigress-group:mainfrom Feb 20, 2026
Conversation
db42291 to
0e8d0f1
Compare
…lt-in plugins - Add pluginImageRegistry and pluginImageNamespace fields to WasmPluginServiceConfig - Support overriding the default registry and namespace in plugins.properties via environment variables - Add HIGRESS_ADMIN_WASM_PLUGIN_IMAGE_REGISTRY and HIGRESS_ADMIN_WASM_PLUGIN_IMAGE_NAMESPACE env support - Update helm values.yaml with pluginServer.imageRegistry and pluginServer.imageNamespace options - Update deployment.yaml to inject the new env vars - Support fallback from pluginServer.imageRegistry to global.hub - Add global.hub and global.pluginNamespace for parent chart integration This allows users to customize the plugin image registry and namespace without modifying plugins.properties. Priority: pluginServer.imageRegistry > global.hub
0e8d0f1 to
8090167
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does
This PR adds support for customizing the plugin image registry and namespace for built-in plugins without modifying the
plugins.propertiesfile.Changes
WasmPluginServiceConfig.java:
pluginImageRegistryandpluginImageNamespacefieldsHIGRESS_ADMIN_WASM_PLUGIN_IMAGE_REGISTRYandHIGRESS_ADMIN_WASM_PLUGIN_IMAGE_NAMESPACEWasmPluginServiceImpl.java:
buildPluginImageUrl()method to construct plugin image URL with custom registry/namespacehelm/values.yaml:
pluginServer.imageRegistryandpluginServer.imageNamespaceoptionsglobal.hubandglobal.pluginNamespacefor parent chart integrationhelm/templates/deployment.yaml:
pluginServer.imageRegistry→global.hubPriority Chain
For plugin image registry:
pluginServer.imageRegistry(direct config)global.hub(parent chart, shared with deployments)For plugin image namespace:
pluginServer.imageNamespace(direct config)global.pluginNamespace(parent chart)Usage
Users can customize the plugin image registry via:
Image URL Transformation
Default URL:
With
global.hub=my-registry.example.com:Related
This PR works together with higress PR #3521 to provide a complete solution for customizing plugin image locations using a shared
global.hubparameter.