[ https://issues.jboss.org/browse/WFWIP-184?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-184: ------------------------------------ I admit there is not strong UseCase for this. I can think just artificiall as reusing existing PVC, complying to company naming convention. I could want to reuse PVC because of migrating from legacy applications to operator approach. And reattach operator pods to the data saved by the previous instances. I just hit this because I was expecting name is required. If not we should inform somehow (in documentation, CRD?) user he doesn't have to (must not) specify name. Best would be to validate somehow in time of saving WildFly CR and return to user meaningful exception. Based on current exception I wouldn't find out what is going on without assistance of my coleague, who hit this before me. Is validation of user input possible in Operator? Does Operator framework provide any support? Is it possible to define some basic validations in CRD? -- This message was sent by Atlassian Jira (v7.13.5#713005)