🌱 Add support for 'ipam' and 'other' providers to tilt

[schrej]

What this PR does / why we need it:
This adds support for 'ipam-' and 'other-' providers to tilt-prepare to allow using ipam or any other new providers with our tilt setup.

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

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign neolit123 after the PR has been reviewed.
You can assign the PR to them by writing /assign @neolit123 in a comment when ready.

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

[vincepri]

/lgtm
/assign @fabriziopandini

[sbueringer]

Q: Is this the PR where we introduce new provider types by introducing ipam- and other- prefixes in addition to the ones we already have for bootstrap/infra/control-plane?

Mostly asking because I'm not aware of that clusterctl or any other part of the code base supports it. (e.g.

cluster-api/cmd/clusterctl/api/v1alpha3/labels.go

Lines 45 to 56 in 477fd77

	func ManifestLabel(name string, providerType ProviderType) string {
	switch providerType {
	case BootstrapProviderType:
	return fmt.Sprintf("bootstrap-%s", name)
	case ControlPlaneProviderType:
	return fmt.Sprintf("control-plane-%s", name)
	case InfrastructureProviderType:
	return fmt.Sprintf("infrastructure-%s", name)
	default:
	return name
	}
	}

)

[schrej]

They are not supported by clusterctl. There is an issue regarding clusterctl support here: #6154
The idea here is to just enable those two kinds of providers to work with tilt for now. We can adapt the tilt config once we've decided how to handle it in clusterctl.

[fabriziopandini]

/hold
Provider and ProviderType are clusterctl constructs, and until there is a proper analysis on what are the impacts of having additional provider types this can potentially prevent us from running clusterctl commands r or from debugging E2E tests (which are using clusterctl internally) on a cluster created with tilt.

As an alternative, we can merge this PR to simplify IPAM provider development, but we should clearly document in the comment/book that this is a temporary solution and it could lead to errors in the scenario described above

[schrej]

I have no idea what changed, and I didn't even notice because I was working with this branch checked out locally for a while, but it seems like this change is no longer necessary. It used to cause errors to have a provider that's not recognised by tilt-prepare, but that error vanished. We probably don't need this anymore.
The following config works fine with this tilt-provider.yaml config: https://github.com/telekom/cluster-api-ipam-provider-in-cluster/blob/main/tilt-provider.yaml

default_registry: localhost:5000
allowed_contexts: ["kind-capi"]
kind_cluster_name: "capi"
provider_repos:
- ../cluster-api-ipam-provider-in-cluster
enable_providers:
# - docker
- ipam-in-cluster
extra_args: 
  core: ["--feature-gates=ClusterTopology=true"]
  kubeadm-bootstrap: ["--feature-gates=ClusterTopology=true"]
  kubeadm-control-plane: ["--feature-gates=ClusterTopology=true"]
  docker: ["--feature-gates=ClusterTopology=true"]
debug:
  ipam-in-cluster:
    port: 30001

I'll reopen in case I run into issues again.