Description of problem:

https://github.com/stolostron/hypershift-addon-operator/issues/85

When running on non-aws platform or (aws platform which fails to be detected properly - see #84) the secret with external-dns configuration fails to be copied. This because the target namespace (hypershift) is only created by the installer if aws platform is detected:

If this code block is skipped, the call to create the secret on the spoke cluster fails due to the missing namespace:

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

How reproducible:

Steps to Reproduce:

1.  
2.  
3. ...

Actual results:

Expected results:

Additional info: