Add externally managed annotations to IBMPowerVSCluster resource

[Karthik-K-N]

What this PR does / why we need it:

This PR adds the filter to IBMPowerVSCluster reosurce to avoid reconciliation if the resource has the externally managed annotation(cluster.x-k8s.io/managed-by) set.
Enhancement: https://github.com/kubernetes-sigs/cluster-api/blob/10d89ceca938e4d3d94a1d1c2b60515bcdf39829/docs/proposals/20210203-externally-managed-cluster-infrastructure.md

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

/area provider/ibmcloud

1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-ibmcloud ready!

Name	Link
🔨 Latest commit	5cce184
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-cluster-api-ibmcloud/deploys/6332b6a9bc86af000917dbc0
😎 Deploy Preview	https://deploy-preview-899--kubernetes-sigs-cluster-api-ibmcloud.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[Prajyot-Parab]

/lgtm

[mkumatag]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Karthik-K-N, mkumatag, Prajyot-Parab

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mkumatag]

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

[mkumatag]

/hold

[mkumatag]

@Prajyot-Parab @Karthik-K-N @dharaneeshvrd can we make sure IBMPowerVSImage delete flow works fine with this flow?

Especially with hypershift project.

[Karthik-K-N]

@Prajyot-Parab @Karthik-K-N @dharaneeshvrd can we make sure IBMPowerVSImage delete flow works fine with this flow?

Especially with hypershift project.

I think it should not affect any other things as we adding externally managed annotations only to IBMPowerVSCluster resource and within that recoincilation we are not doing anything other than setting ready status to true.

[mkumatag]

@Prajyot-Parab @Karthik-K-N @dharaneeshvrd can we make sure IBMPowerVSImage delete flow works fine with this flow?
Especially with hypershift project.

I think it should not affect any other things as we adding externally managed annotations only to IBMPowerVSCluster resource and within that recoincilation we are not doing anything other than setting ready status to true.

I'm have concern about the delete flow because we are deleting them when delete cluster triggered.

[dharaneeshvrd]

@mkumatag As you expected, in hypershift delete flow ibmpowervsimage did nt get deleted, due to that whole deletion got stuck(hosted control plane namespace and due to that hosted cluster).

fyi @Karthik-K-N @Prajyot-Parab

[Karthik-K-N]

/hold

[mkumatag]

@Karthik-K-N #938 is merged, hence can this be merged as well?

[Karthik-K-N]

@Karthik-K-N #938 is merged, hence can this be merged as well?

Yes.

[mkumatag]

/unhold