Update libvirt cluster-api provider config version

[bison]

With the move to the kubebuilder CRD based cluster-api components, the
API version for the libvirt provider config subresources has changed
to: libvirtproviderconfig.k8s.io/v1alpha1

[abhinavdahiya]

What PR made that change in cluster-api-provider-libvirt?

[abhinavdahiya]

/approve

[bison]

I think it was openshift/cluster-api-provider-libvirt#72. That was merged into the crd branch, which is what is being deployed now I guess.

[abhinavdahiya]

@bison where did you get libvirtproviderconfig.k8s.io/v1alpha1 ?
https://github.com/openshift/cluster-api-provider-libvirt/blob/master/pkg/cloud/libvirt/providerconfig/v1alpha1/register.go#L35-L39 this has the old api group name.

[bison]

@abhinavdahiya check the crd branch not master. We're in the middle of the migration from aggregated API to CRDs, so we're on this CRD branch for now.

@enxebre and @ingvagabund probably know more about the plan / timing there if you have questions on that.

[bison]

I'm pretty sure the e2e failure is unrelated to this... I'll try again though

/test e2e-aws

[ingvagabund]

The new provider config (for both aws and libvirt) were generated by the kubebuilder command. Even @enxebre 's migrated aws actuator has the k8s.io suffix: https://github.com/openshift/cluster-api-provider-aws/blob/crd/pkg/apis/awsproviderconfig/v1alpha1/register.go#L39

[rphillips]

/test e2e-aws

[enxebre]

/test e2e-aws

[bison]

/test e2e-aws

[abhinavdahiya]

Can you post the error from e2e before you retest.

[bison]

Sure, the last one was aborted, so I didn't see much worthwhile. I'll post the results of the current run.

[sjenning]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, bison, sjenning

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

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