Description of problem:
The acm-simple-kmod does not create the namespace on spoke cluster.

Version-Release number of selected component (if applicable):
release-4.11

How reproducible:


Steps to Reproduce:
1. Deploy acm-simple-kmod example on a hub/spoke
2.
3.

Actual results:

The policy status stays as NonCompliant

"status": [
            {
                "clustername": "sno1-0",
                "clusternamespace": "sno1-0",
                "compliant": "NonCompliant"
            },
            {
                "clustername": "sno2-0",
                "clusternamespace": "sno2-0",
                "compliant": "NonCompliant"
            }
        ]

While looking on the spoke cluster, there were no acm-simple-kmod namespace where to run the container. 

Then I created the namespace by hand on the sno1-0 spoke:
# KUBECONFIG=/sno1-0/auth/kubeconfig oc new-project acm-simple-kmod

Rechecked the policy and this time the sno1-0 is compliant:

        "status": [
            {
                "clustername": "sno1-0",
                "clusternamespace": "sno1-0",
                "compliant": "Compliant"
            },
            {
                "clustername": "sno2-0",
                "clusternamespace": "sno2-0",
                "compliant": "NonCompliant"
            }
        ]

Then checked the pods in the acm-simple-kmod namespace:
KUBECONFIG=/sno1-0/auth/kubeconfig oc get pods 
NAME                                                 READY   STATUS    RESTARTS   AGE
acm-simple-kmod-4-18-0-305-25-1-el8-4-x86-64-nv8rg   1/1     Running   0          7m25s


Expected results:
Example to create the namespace for the container

Additional info: