clustercatalog is a cluster scoped resource and it does not need to have namespace mentioned in its yaml file. Currently below is how it is been seen.

{code:java}
apiVersion: olm.operatorframework.io/v1
kind: ClusterCatalog
metadata:
  name: cc-redhat-operator-index-v4-17
  namespace: openshift-marketplace
spec:
  priority: 0
  source:
    image:
      ref: ec2-3-137-182-27.us-east-2.compute.amazonaws.com:5000/cc/redhat/redhat-operator-index:v4.17
    type: Image
status: {}

    Version-Release number of selected component (if applicable):{code:none}
     4.18
    

     Always
    

    1. Mirror an imageSetConfig as shown below with the PR which has fix for clusterCatlaog
    
{code:java}
kind: ImageSetConfiguration
apiVersion: mirror.openshift.io/v2alpha1
mirror:
  operators:
  - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.17
    packages:
    - name: security-profiles-operator

    Actual results:{code:none}
     Generating ClusterCatalog yaml has namespace as shown in the description.
    

     There should not be any namespace in the yaml file since clustercatalog is a cluster scoped resource.
    

    https://redhat-internal.slack.com/archives/C050P27C71S/p1738324252074669?thread_ts=1738322462.210089&cid=C050P27C71S