Deploy your plugin on a cluster
After pushing an image with your changes to a registry, you can deploy the plugin to a cluster by using a Helm chart.
-
You must have the location of the image containing the plugin that was previously pushed.
You can specify additional parameters based on the needs of your plugin. The
values.yamlfile provides a full set of supported parameters.
-
To deploy your plugin to a cluster, install a Helm chart with the name of the plugin as the Helm release name into a new namespace or an existing namespace as specified by the
-ncommand-line option. Provide the location of the image within theplugin.imageparameter by using the following command:$ helm upgrade -i my-plugin charts/openshift-console-plugin -n my-plugin-namespace --create-namespace --set plugin.image=my-plugin-image-locationWhere:
n <my-plugin-namespace>-
Specifies an existing namespace to deploy your plugin into.
--create-namespace-
Optional: If deploying to a new namespace, use this parameter.
--set plugin.image=my-plugin-image-location-
Specifies the location of the image within the
plugin.imageparameter.
If you are deploying on Red Hat OpenShift Container Platform 4.10 and later, it is recommended to exclude configurations related to pod security by adding the parameter
--set plugin.securityContext.enabled=false. -
Optional: You can specify any additional parameters by using the set of supported parameters in the
charts/openshift-console-plugin/values.yamlfile.plugin: name: "" description: "" image: "" imagePullPolicy: IfNotPresent replicas: 2 port: 9443 securityContext: enabled: true podSecurityContext: enabled: true runAsNonRoot: true seccompProfile: type: RuntimeDefault containerSecurityContext: enabled: true allowPrivilegeEscalation: false capabilities: drop: - ALL resources: requests: cpu: 10m memory: 50Mi basePath: / certificateSecretName: "" serviceAccount: create: true annotations: {} name: "" patcherServiceAccount: create: true annotations: {} name: "" jobs: patchConsoles: enabled: true image: "registry.redhat.io/openshift4/ose-tools-rhel8@sha256:e44074f21e0cca6464e50cb6ff934747e0bd11162ea01d522433a1a1ae116103" podSecurityContext: enabled: true runAsNonRoot: true seccompProfile: type: RuntimeDefault containerSecurityContext: enabled: true allowPrivilegeEscalation: false capabilities: drop: - ALL resources: requests: cpu: 10m memory: 50Mi
-
View the list of enabled plugins by navigating from Administration → Cluster Settings → Configuration → Console
operator.openshift.io→ Console plugins or by visiting the Overview page.
|
|
It can take a few minutes for the new plugin configuration to appear. If you do not see your plugin, you might need to refresh your browser if the plugin was recently enabled. If you receive any errors at runtime, check the JS console in browser developer tools to look for any errors in your plugin code. |