Rob Cernich

@ostromart, cluster admin just installs the operater. A mesh admin (designated by cluster-admin) manages the control plane entirely: creates namespace, creates CR, etc. This mesh admin should be managing the...

Hey @jmazzitelli, nothing prevents namespace admins from interacting with those objects and currently we don't watch for changes of those resources to overwrite any changes made by somebody other than...

Cluster scoped resources and resources in other namespaces cannot have owner references, which is why the finalizer would be necessary.

Could you elaborate on the "stuck finalizer" problem? In the original comment, you say that the resource remains when the operator is deleted. The simple answer is: don't delete the...

Don't delete the operator is a _requirement_ if you're using the operator. If you're talking about a single user, who is doing everything as cluster-admin, with a single install, no...

I'm not sure what the issue might be. I'm not familiar with those tests, but it looks like it's doing a docker build on src/test/resources/wildfly/DockerfileTemplate and using the resulting image...

Is the issue related to the order in which the resources are deleted? It almost seems like the user is getting nuked before it removes everything else. Regarding random failures,...

Added support for a "cubeId" property on the container configuration. This should default to the container name if no cubeId is specified.

Ordering should be a high priority to ensure module dependencies are applied before the module depending on them. For example, if module A requires module B, module B should be...

I think things like this would have specialized merge code. For the example above, I don't think it makes sense to merge the command list at all. Instead, one would...