Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't install provider from private registry #179

Open
migueladh opened this issue Mar 15, 2024 · 1 comment
Open

Can't install provider from private registry #179

migueladh opened this issue Mar 15, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@migueladh
Copy link

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 :)

@migueladh migueladh added the bug Something isn't working label Mar 15, 2024
@Alegrowin
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants