---
name: openshift-ts-cluster-sbd-image-stream
title: Why don't image streams populate on a secure by default cluster?
description: You completed the steps to allow outbound traffic to image streams, but image streams do not populate on a secure-by-default cluster.
last-updated: 2026-04-14
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/openshift?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why don't image streams populate on a secure by default cluster?
{: #ts_cluster_sbd_image_stream}
{: support}

You completed the steps to [allow outbound traffic to image streams](https://cloud.ibm.com/docs/openshift?topic=openshift-sbd-allow-outbound&format=markdown#sbd-example-is), but image streams do not populate on a secure-by-default cluster.
{: tsSymptoms}

In the console, when you navigate to the **Import from Git** page and check the **Builder Image** section, you see an `Unable to detect the Builder Image` error.


Image streams are populated from a public registry. On a secure-by-default cluster, public access is blocked. If you disable traffic protection after the cluster is created, the image streams are not populated. The Cluster Samples Operator configuration management state is then incorrectly reported as `Removed`.
{: tsCauses}


Update the Cluster Samples Operator configuration management state to fix the issue.
{: tsResolve}

1. Run the following command:
    ```sh
    oc edit configs.samples.operator.openshift.io cluster
    ```
    {: pre}

1. Change the `Removed` value to `Managed`.

1. Repeat this change for each affected instance.

1. In the console, refresh the **Import from Git** page.