Michael Edgar

> > Ultimately, the CRD schema will either be rejected or it will not validate as expected > > As far as I can tell, in this repo, we have...

> * with a typed API -> I expect full support by the tooling > * with a plain string -> I know that I'm using an escape hatch that...

At this point it seems unlikely for this PR to be merged as-is. Based on the feedback so far, is the thinking that the annotation should contain simply a string...

> Are you proposing an annotation that would replace the entire schema for a given field or type? Would there also be a way to overlay / patch the generated...

Closing for now to declutter. Let me know if this is something to explore again in the future.

Would `quarkus.operator-sdk.generate-with-watched-namespaces` help with the operator's own service account? I could be missing what that property is meant to be used for.

Suppose I use `quarkus.kubernetes.rbac.service-accounts.my-service-account.namespace=my_namespace` to set the service account/namespace for an operator where the deployment name is `my-operator`. In the generated CSV the operator deployment's `serviceAccountName` is `my-service-account`, but the...

> If you generate a `my-service-account` SA, wouldn't it be the name used in your operator's deployment, though? How would the link between both be made? Yeah, that's what happens,...

Hi @cpotter1 , the "END" events are currently signaled at the start of the following segment but the "START" events do provide the starting segment name in the position information....

`ST` is the start of a transaction, `SE` is the end. One transaction per `ST`/`SE` pair.