Jared Watts

https://github.com/crossplane/crossplane/pull/6549 looks to be addressing this issue

the upjet template repo has an example installation manifest that uses a default registry - that should be updated to use an explicit registry: * https://github.com/crossplane/upjet-provider-template/blob/main/examples/install.yaml

x-ref to https://github.com/crossplane/crossplane/issues/2672#issuecomment-2827053218 - this issue is still a good idea 😇

This URL isn't an OCI repository and I don't think it's set up for Helm OCI stuff, so is this actually expected to work? Or would we need to update...

The import process using an ObserveOnly resource you linked to in [the docs](https://docs.crossplane.io/latest/guides/import-existing-resources/#import-resources-automatically) is the common import path that folks use and it does work reliably well. However, as you...

From the conversation during PR review (https://github.com/crossplane/crossplane-runtime/pull/683#discussion_r1550609074), it seemed like specifying the resource name for these count metrics was not acceptable cardinality wise. I've viewed these metrics as just a...

/fresh thanks for this contribution @Avarei! I think it's still relevant and hopefully we can finish it off in the v1.20 milestone 🙇

@avarei, I was coming back to this PR now with v2.1 approaching, but immediately thought of all the confusion right now around XR connection details no longer being supported: *...

``` +helm-setup *failed* | curl: (6) Could not resolve host: get.helm.sh ``` oh fun, i've seen this in a few places today and we believe it to be an impact...

Thanks for sharing this observation. It also looks like the instructions when clicking the `INSTALL` button on https://artifacthub.io/packages/helm/crossplane/crossplane default to the `master` channel too. Do you have any idea where...