Any plan to cut a v0.1.0 release?

[fabriziopandini]

This will unblock kubernetes-sigs/cluster-api#8811, so we can get this provider accessible via clusterctl

[mcbenjemaa]

I'm looking to become a maintainer for this ipam provider.

[schrej]

We are planning to, yes. I was mainly waiting for #203 which we finally merged a few days ago. There is a few things left, but then we'll at least cut a release candidate.
I'm considering to jump to 1.0.0 directly, as we're probably pretty feature complete. The only concern would be stability. I'd rely on some feedback from VMware to decide on that, since they've been using it a lot more (= at all) than we have.

@mcbenjemaa great! we're a bit understaffed, would be great to have a few more. Shouldn't be too much work form now on either.

[stmcginnis]

I'm guessing this is a sign of some progress here? :)

Error: failed to get provider components for the "in-cluster" provider: failed to get repository client for the IPAMProvider with name in-cluster: error creating the GitHub repository client: failed to get latest release: release not found for version v0.1.0-rc.0, please retry later or set "GOPROXY=off" to get the current stable release: 404 Not Found

[schrej]

Yep! Just waiting for the image: kubernetes/k8s.io#6393 (and I also need to fix the manifests)