Daniel Mangum

@parul5sahoo is correct here 👍🏻 Crossplane maintains a separate cache than the node's container runtime, so if you populate the cache and use `packagePullPolicy: Never`, Crossplane should always use that...

@jbw976 totally happy to defer this to someone else! This would be an incredibly helpful effort for us and pretty much any project that is consuming the credential providers via...

Wanted to follow up on a few assertions here: > Users have to deploy their own in-cluster registry This is one option, but certainly not the only one. The [Crossplane...

@MisterMX I have not made any progress here yet, and I would be happy for you to work on it :) Some initial thoughts: - Today this can be worked...

> Perhaps this is a non-issue for me if someone could explain whether or not I should be concerned about "unintended consequences"? @zonybob Unintended consequences in this case just means...

> Would overwriting the default registry make Crossplane pull the default provider packages from a custom registry instead of DockerHub? @MisterMX it would 👍🏻 you can set it with `--set...

@mf-lit your Crossplane version is listed as `1.13.0`, which is not an existing version. Did you mean `1.3.0` or possibly `1.1.3`? Also, would you be able to provide (obscured) managed...

Also noting here from #2253: > This particular XR is for SQS queues, we have other XRs (for IAM and RDS for example) that have no problem with this. (So...

Posting here to help any other folks that run into this. With `WAYLAND_DEBUG=1`, you can see the following logs prior to crash: ``` [3039631.157] -> [email protected]_immed(new id wl_buffer@30, 1071, 397,...

@erik-kz sorry about that! I don't see that specific call, but here is the full wayland debug output: ``` [3039581.410] -> [email protected]_surface(new id wl_surface@27) [3039581.494] -> [email protected]_surface(new id wl_surface@29) [3039581.696]...