The dynamic plugins set in the operator config are not being loaded on console startup. Only plugins loaded in development mode are being activated. The frontend should initialize all plugins through the console proxy on load instead of loading the URLs directly.
1. Deploy console-demo-plugin on OpenShift cluster
[yapei@New_Mac dynamic-demo-plugin]$ oc apply -f oc-manifest.yaml
$ oc get pods -n console-demo-plugin
NAME READY STATUS RESTARTS AGE
console-demo-plugin-c9674944c-9r9fn 1/1 Running 0 5m4s
2. enable the demo plugin and save the changes
$ oc edit console.operator.openshift.io cluster
3. wait for new console pods created and running
4. check cm/console-config YAML to see if plugin settings are updated
$ oc get cm console-config -n openshift-console -o yaml | grep plugins -A1
5. open console URL and inspect window.SERVER_FLAGS.consolePlugins via browser console, it returns console-demo-plugin
console-demo-plugin is automatically loaded, verified on 4.7.0-0.nightly-2021-02-03-165316
We can see some logs:
Loading entry script for plugin email@example.com from https://console-openshift-console.apps.qe-ui48-0220.qe.devcluster.openshift.com/api/plugins/console-demo-plugin/plugin-entry.js
Added plugin firstname.lastname@example.org
Plugin email@example.com is now enabled
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.