Based on the fetched infromation from OpenShift CI we run the fence_aws FA

Check the FAR logs that indicate a successful CLI executation to verify that the fence agent has been running successfully

Automate FA selection and creation based on the platform it use - AWS or BMH

CRs are namepsaced, thus they should reside next to the operator. Action status is used to demonstrate the use case of fence_aws

Remove a prefix from the Provider ID for having the instance ID per machine

Instead of hard code the namespace of where the operator is installed just fetch the environment variable OPERATOR_NS so FAR CRs will be created on the same namespace that FAR operator has been installed

PR medik8s#42 add downward API which makes some code redundant

Meaningful and less confusing import names, and signal for GetDeploymentNamespace failure but don't faile e2e/ut test

Bad practice

Due to code-review