Allow rsct pods to be deployed in any namespace

[sats-23]

Fixes #76

Status:
Operator comes with a SA (rsct-operator-controller-manager) under NS (rsct-operator-system).
RSCT CR comes with a SA (rsct) under fixed NS (rsct-operator-system).

Solution:
-Provide SA (rsct-operator-controller-manager) with RBAC permissions to be able to patch SCC on behalf of SA (rsct).
-The controller's reconcile logic grants the SA (rsct) with privileged SCC.
-Now rsct pods can be deployed into any NS without having to manually deploy CR and CRB.

Test Operator image: sats23/sats:rsct

[ppc64le-cloud-bot]

Welcome @sats-23! It looks like this is your first PR to ocp-power-automation/rsct-operator 🎉

[sats-23]

/cc @varad-ahirwadkar

[ppc64le-cloud-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sats-23
Once this PR has been reviewed and has the lgtm label, please assign mkumatag for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ppc64le-cloud-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sats-23
Once this PR has been reviewed and has the lgtm label, please assign mkumatag for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sats-23]

@mkumatag @varad-ahirwadkar Please have a look with the new approach
#140 (comment)

[varad-ahirwadkar]

Hi @sats-23 .
Since the implementation imports github.com/openshift/api and relies on SecurityContextConstraints (SCC), will this operator still work on a Kubernetes cluster?

As SCCs are OpenShift-specific, I'm wondering if this change restricts the operator to OpenShift only, or if we should consider a fallback mechanism check for broader compatibility.

[sats-23]

Hi @sats-23 . Since the implementation imports github.com/openshift/api and relies on SecurityContextConstraints (SCC), will this operator still work on a Kubernetes cluster?

As SCCs are OpenShift-specific, I'm wondering if this change restricts the operator to OpenShift only, or if we should consider a fallback mechanism check for broader compatibility.

Hi @varad-ahirwadkar, please refer to c82ce64 for the fallback logic

[varad-ahirwadkar]

/lgtm