MorningSpace

@gustavonalle I was looking for a `dind`-based solution for OpenShift multiple-node cluster launch to embed into my [lab-k8s-playground](https://github.com/morningspace/lab-k8s-playground)... then come across here... Really love this project... but unfortunately, it appears...

Yeah, actually I am looking at `crc`, which looks to be the official approach recommended by Red Hat. But it seems to be single node rather than multiple nodes. Also,...

@Daniel-Fan @horis233 Any comment on that? Is this a desired behavior, or something could be addressed?

Thanks @horis233. To decouple the OperandRequest w/ OperandRegistry and OperandConfig, that makes sense to me. Before that, I guess I would keep OperandRegistry and OperandConfig there when I delete OperandRequest....

Thanks, I see it's been opened for a while, wonder when will this be merged :-)

@raffaelespazzoli > Plus you can always create a patch per target object. Indeed, this is actually what I was doing to mitigate the issue. Interestingly, I did some quick simple...

Thanks @raffaelespazzoli for your quick response! It sounds great, but I did a quick try and was not able to make it work in some cases. What I tried is...

Thanks @dmathieu for your reply! * It was mentioned in [semantic conventions](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/runtime/go-metrics.md) that [go.memory.allocated](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/runtime/go-metrics.md#metric-gomemoryallocated) is the memory allocated to the heap by the application, while in `runtime.memStats`, it has both...

Hi @dashpole, thanks for your reply and sorry for the delay. I spent a few hours today to revisit the materials mentioned in the above thread. Here's my findings and...

Thanks @dashpole ! I like the idea of "add some metrics which are disabled by default, with options to enable them", so that's the end user who determines whether the...