> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/kubernetes-security/onboard-the-kubernetes-connector/openshift-container-registry.md).
# OpenShift container registry
The OpenShift Container Registry provides visibility into the container images stored within your OpenShift environment. When you deploy the Kubernetes Connector on an OpenShift platform, the system automatically discovers and creates registry instances for monitoring.
When adding an instance of Kubernetes from **Data Sources & Integrations**, the setting **Registry Scanning (OpenShift Only)** must be configured to enable automatic scanning of an OpenShift container registry. By default, scanning operates in a concurrency-limited mode (10 images at a time) to minimize resource impact on the cluster while maintaining thorough security coverage.
Manage OpenShift registry instances
You can view and manage the registry instances automatically created by your OpenShift Kubernetes deployment.
* Data source page: Displays a list of all discovered OpenShift registry instances.
* Key details: For each instance, you can quickly see the status, instance name, and associated cluster name.
View instance details
To gain deeper insights into a specific registry, click on one of the instances from the table of the **OpenShift Container Registry**. This opens a page that includes detailed information about the particular instance.
The detailed dashboard provides the following information:
* **Status**: The current operational state of the registry instance.
* **Kubernetes Connector Status**: Indicates the health and connectivity of the connector managing the registry.
* **Repositories**: The total count of image repositories discovered within the registry.
* **Scan Mode**: Displays the current scanning configuration.
* **Registry Scanning**: Shows the real-time status of the cluster. Click on the **Status**, which navigates you to a dashboard that shows the total number of assets and their current status, and the **Health Audits** of the specific cluster.
Repository inventory
The instance details page includes a granular list of all repositories found within the OpenShift registry. This list includes:
* **Name**: The identifier for the specific image repository.
* **Repository Type**: Categorization of the repository within the OpenShift environment.
Actions
From the top left side of the page, click the More Options () to:
* **Exclude/Include images**: You can configure scoping rules to include or exclude specific images and repositories from scans based on their names or tags. While updates apply to all future scans, previously excluded images will only be processed during a subsequent system-wide rescan.
* **Discover Now**: Triggers the discovery and then scanning of newly discovered assets.
Access OpenShift from Kubernetes
You can also view important details about your OpenShift registry from the Kubernetes data source. From the list of clusters in the Kubernetes table, select the OpenShift registry to view:
* **Connector Details**: Shows last scan, connector status and connector version of the OpenShift platform.
* **Cluster Details**: Click the link to view the asset card of the [OpenShift cluster](/kubernetes-security/kubernetes-clusters.md).
* **Deployment Details**: Shows deployment method used and the deployment date.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/kubernetes-security/onboard-the-kubernetes-connector/openshift-container-registry.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.