Chris Laprun

> I don't follow you: when testing this, the application name is `>`, but when doing a real build, it will use the module name. `>` is not a valid...

You cannot set the application name if you're using `QuarkusTest` only.

I agree that it shouldn't cause an issue in most cases. However, this shows that there are at least 2 issues with the code that deals with this: 1. improper...

Do you have a way to replicate the issue?

Does it still happen with Quarkus 2.9.0?

Weird. Let us know if you figure something out…

This should already be covered: you can configure which namespace(s) the operator needs to watch so it should already be able to monitor custom resources in namespace(s) other than the...

OK, makes sense.

Presumably people writing operators know how to connect to a cluster… 😁 Personally, I test with kind and I use kubectx/kubens to deal with connecting to the cluster. Feel free...

Would it be possible to provide me with an example file that you'd like the extension to proceed?