Can't install provider from private registry

[migueladh]

What happened?

When moving original image from xpkg.upbound.io to an internal repository and installing the provider, the provider fails to start, since it's referencing the controller image in package/crossplane.yaml (even though the provider is mono-image and injects runtime on build)

How can we reproduce it?

Try to run the provider on a k8s cluster with no access to public repos.

What environment did it happen in?

Crossplane version: all

If

  controller:
    image: xpkg.upbound.io/linode/provider-ceph:v0.0.40

gets removed from package/crossplane.yaml, provider will default to start embedded runtime :)

[Alegrowin]

If that can unblock you,
I solved for the same yesterday, had to bump the version in package/crossplane.yaml before running crossplane xpkg push -f _output/xpkg/linux_amd64/provider-ceph-v0.0.0-486.gea34efd.dirty.xpkg docker.io/user/provider-ceph:v0.0.50

[KarlisAG]

It would be really great if this got some attention - I would assume many environments are restricted to use private registries and this makes the whole provider unusable. I see that other crossplane providers don't have the controller.image specified - maybe that would be the reason they take the image you specify in the Provider? @nolancon Is this something we can ask of you?

Also @Alegrowin how did you get the file locally under _output? What commands were used? I can't seem to even run the basic make commands as it just gives errors of missing rules in the Makefile