Andrea Peruffo
Andrea Peruffo
Hi @loicmathieu , do you mind sharing how to reproduce the issue on our side? Meanwhile, I find this comment possibly relevant: https://stackoverflow.com/a/4162685 We are using H2 version `1.4.199` so...
cc. @hoffrocket
+1 on keeping the original `apt` behaviour and generating the CRD for all the available annotated classes.
I'm using `3.0.0-SNAPSHOT`
From the code: https://github.com/quarkiverse/quarkus-operator-sdk/blob/5119c1f817aa66b3f8583f7b26b2147a33a90e61/core/deployment/src/main/java/io/quarkiverse/operatorsdk/deployment/AddRoleBindingsDecorator.java#L83 this is still generating a `null` namespace in case I don't have a globally defined one (which I would like to avoid since people should be...
Yes there is a warning: ``` 'realmcontroller' controller is configured to watch all namespaces, this requires a ClusterRoleBinding for which we MUST specify the namespace of the operator ServiceAccount. This...
The end goal is to deploy Cluster wide, but watching one namespace is useful for testing e.g.
I want it to be easily customizable by end users. But I think I found a "good enough" solution using `kustomize` this is the reference: https://github.com/keycloak/keycloak/pull/9535/files#diff-4d0b1eae1d906945a05e18bb92e698ea12a17c092c169e6f665d556c552d9a2fR4-R24 which is: - use...
I do believe that the end user of an operator will not even know that the operator runs on Quarkus and they just want to deploy it using some "standard"...