OCP Integration
The ocp4_workload_ocp_console_embed role makes it possible to embed the OpenShift web console inside a Showroom tab as an iframe.
By default, OpenShift sets security headers (X-Frame-Options, Content-Security-Policy) that prevent iframing.
This role works around that limitation.
ocp4_workload_showroom_ocp_integration is deprecated.
Use ocp4_workload_ocp_console_embed instead — it is a drop-in replacement.
|
Add the role to your workloads list before the main ocp4_workload_showroom role:
workloads:
- agnosticd.showroom.ocp4_workload_ocp_console_embed
- agnosticd.showroom.ocp4_workload_showroom
ocp4_workload_ocp_console_embed
This role deploys a lightweight webhook proxy that intercepts OpenShift console responses and strips the headers that prevent iframing. It runs as its own deployment in a dedicated namespace.
Variables
| Variable | Type | Default | Description |
|---|---|---|---|
|
string |
|
GUID for the deployment. |
|
string |
|
Apps domain for routing. |
|
string |
|
Namespace where the proxy runs. |
|
string |
|
Name for the deployment and service. |
|
string |
|
Container image for the webhook proxy. |
When You Do Not Need This Role
If your lab does not include an OCP console tab in ui-config.yml, you do not need this role.
It is only necessary when you want to embed the OpenShift web console as an iframe tab in Showroom.
Working Example
The tests/showroom-ocp4 catalog item uses ocp4_workload_ocp_console_embed alongside the main Showroom workload:
workloads:
- agnosticd.showroom.ocp4_workload_ocp_console_embed
- agnosticd.showroom.ocp4_workload_showroom
Further Reading
-
UI Configuration — configure the OCP Console tab.
-
OCP4 Role Reference — the main Showroom OCP4 role.