Description of problem:

Once installed OCP, ACM and GitOps operator we face an issue when we use the pre and post hooks from https://github.com/openshift-kni/cnf-features-deploy/ztp/gitops-subscriptions/argocd.

The behaviour is:

- We load the deployment folder as the README.md says
- Our DU manifests (clusters and policies) are being loaded using Argo
- When the PolicyGen tries to execute the hooks an unauthorized error appears

Pre Hook
```
[root@bastion1 gitops-verizon]# oc logs siteconfig-pre-6ncnx
error: failed to create configmap: Unauthorized
ztp-hooks.presync Wed, 15 Sep 2021 13:02:10 +0000 ERROR [pre-sync-entrypoint] Config map of siteconfigs resourceVersion creation failed
```

So we debug the pod and enter in to that, the force the execution sourcing the common.sh to force login into OCP cluster and then the clusters are being loaded, but it appears again on the post hook

Post Hook
```
[root@bastion1 gitops-verizon]# oc logs siteconfig-post-9zksw
ztp-hooks.postsync Wed, 15 Sep 2021 13:04:27 +0000 ERROR [post-sync-entrypoint] Failed to get RAN sites resourceVersion
ztp-hooks.watcher 2021-09-15 13:04:28 UTC [DEBUG]             [watcher:217]: 0, siteconfigs
ztp-hooks.watcher 2021-09-15 13:04:28 UTC [ERROR]             [watcher:53]: (401)
Reason: Unauthorized
HTTP response headers: HTTPHeaderDict({'Audit-Id': '56919b9c-db7f-4d6f-a9a4-7916f94777d9', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'Date': 'Wed, 15 Sep 2021 13:04:28 GMT', 'Content-Length': '129'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}

Traceback (most recent call last):
  File "watcher.py", line 51, in watch_resources
    resource_version=rv, timeout_seconds=5)
  File "/usr/local/lib/python3.6/site-packages/kubernetes/client/api/custom_objects_api.py", line 2087, in list_cluster_custom_object_with_http_info
    collection_formats=collection_formats)
  File "/usr/local/lib/python3.6/site-packages/kubernetes/client/api_client.py", line 353, in call_api
    _preload_content, _request_timeout, _host)
  File "/usr/local/lib/python3.6/site-packages/kubernetes/client/api_client.py", line 184, in __call_api
    _request_timeout=_request_timeout)
  File "/usr/local/lib/python3.6/site-packages/kubernetes/client/api_client.py", line 377, in request
    headers=headers)
  File "/usr/local/lib/python3.6/site-packages/kubernetes/client/rest.py", line 243, in GET
    query_params=query_params)
  File "/usr/local/lib/python3.6/site-packages/kubernetes/client/rest.py", line 233, in request
    raise ApiException(http_resp=r)
kubernetes.client.exceptions.ApiException: (401)
Reason: Unauthorized
HTTP response headers: HTTPHeaderDict({'Audit-Id': '56919b9c-db7f-4d6f-a9a4-7916f94777d9', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'Date': 'Wed, 15 Sep 2021 13:04:28 GMT', 'Content-Length': '129'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}


ztp-hooks.watcher 2021-09-15 13:04:28 UTC [ERROR]             [watcher:223]: 'NoneType' object is not subscriptable
Traceback (most recent call last):
  File "watcher.py", line 221, in <module>
    ApiResponseParser(resp, resourcename=sys.argv[2], debug=debug)
  File "watcher.py", line 122, in __init__
    if api_response[1] != 200:
TypeError: 'NoneType' object is not subscriptable
```

If we repeat the same workaround, debugging the node and forcing the generation it works.

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

OCP: 4.8.12
ACM: 2.3.3-7
Openshift-gitops Operator: latest from channel 4.8
Platform: IPv6/Disconnected


How reproducible:

- always

Steps to Reproduce:
1. Create the NS and Secrets for your clusters
2. Have the repo update with the clusters definitions
3. clone https://github.com/openshift-kni/cnf-features-deploy and fill the https://github.com/openshift-kni/cnf-features-deploy/tree/master/ztp/gitops-subscriptions/argocd/deployment/{policies-app.yaml,cluster-app.yaml}
3. execute oc apply -k on deployment folder

Actual results:

It fails the most of the times (90%)

Expected results:

work most of the times.
Additional info: