⚠️ align prefix of deployments with image name

[schrej]

What this PR does / why we need it:
Replaces the caip-in-cluster prefix with capi-ipam-in-cluster to be in line with the future image name. It was pointed out that caip just looks like a misspelling of capi.

I think this will lead to issues when upgrading existing deployments with clusterctl and would require to manually uninstall the provider first.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: schrej

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 [schrej]

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

[rikatz]

/lgtm
/hold

Unhold as you wish :)

Gave a headsup on it for my colleagues as well! Thanks!

[schrej]

Thanks. Then we'll just have to remember putting this into release notes. Should only require a manual removal of the old resources. Since CRDs can stay, no data should be lost.

/unhold

[agtogna]

[...] Should only require a manual removal of the old resources. Since CRDs can stay, no data should be lost.

I desume it can't be upgraded via clusterctl. What is the correct way to upgrade then?
Could we completely remove the "old" caip-in-cluster-system namespace and then upgrade the IPAM component via clusterctl? e.g.

kubectl delete namespace caip-in-cluster-system
clusterctl upgrade apply --ipam incluster:v0.1.0-rc.0

[schrej]

Yeah, that should work. I haven't tested it though.

[agtogna]

the correct way to do it is:

kubectl delete namespace caip-in-cluster-system
clusterctl init --ipam incluster:v0.1.0 --config clusterctl-IPAM.config.yaml

where clusterctl-IPAM.config.yaml is:

---
providers:
  - name: incluster
    url: https://github.com/kubernetes-sigs/cluster-api-ipam-provider-in-cluster/releases/latest/ipam-components.yaml
    type: IPAMProvider

[schrej]

clusterctl v1.7 should no longer require the extra configuraiton.