Function spec.package does not use cluster local image cache about crossplane

[smoehrle]

Ah, thanks for pointing that out. I edited the places where I missed the replacement. This is only a mistake here in the issue 😇

[phisco]

Loading the image in the cluster won't be enough, as Crossplane too needs to pull the image first, you'll also need to follow this: https://docs.crossplane.io/latest/concepts/packages/#install-offline

[smoehrle]

Thanks for the hint! Though, I haven't tried it yet.

But what about local registries? Is there a possibility to configure crossplane such that I can use a local registry via http?

[phisco]

You definitely can, you "just" need to spin up a registry container in the same network as the kind cluster, push your images there and properly configure the dns to allow crossplane and nodes to reach it 😅

[smoehrle]

I have, but it doesn't work.

• In a second attempt I set up a kind local registry. I verified the registry with docker exec kind-worker crictl pull localhost:5000/function-demo:v0.1.0. I could access and pull from the registry.

Like I mentioned in the first post, I set up a local registry in a second attempt. It is either accessible via localhost:5000 (from the kind docs) and also via kind-registry:5000. I also verified, that the kind nodes can pull from that registry.

The problem with this approach is, that crossplane cannot access this registry because it keeps trying via https and not via http. For kind, there are config options to change this behavior, but I haven't found any for crossplane. So are there any options to change that?

[phisco]

For sure using localhost:5000 as spec.package in the Function won't work. But I guess you tried also with kind-registry.

[smoehrle]

Yes tested it with kind-registry or the IP directly:

This is the error message:

Failed to pull image "kind-registry:5000/function-demo:v0.1.0": failed to pull and unpack image "kind-registry:5000/function-demo:v0.1.1": failed to resolve reference "kind-registry:5000/function-demo:v0.1.0": failed to do request: Head "https://kind-registry:5000/v2/function-demo/manifests/v0.1.0": http: server gave HTTP response to HTTPS client

[jbw976]

In the hopes that we don't overlook something small, I noticed that we use function-demo for the load:

kind load docker-image localhost:5000/function-demo:v0.1.0

Then the function spec uses function-xusers:

package: localhost:5000/function-xusers:v0.1.0

Just wanted to make sure that difference was expected and not overlooked 😇

[github-actions]

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.