Description of problem: `oc create route` relies on connection to the server to perform all validation, So during dry-run and attempting to output a route object erroneous values will not be checked.
RamR observes: @knobunc adding some of these checks on client side could be problematic. One is that older cli clients would behave differently vis-a-vis newer cli clients + what happens when the server validation changes say for a list of choices from [foo, bar] to [foo, bar, baz] or even [one, two]? The older cli client checks would be invalid at that point or worse yet even block valid values.
Clayton says: We need less client side validation, and more serverside. Clients should not make decisions about valid values. -- Based on that, I'm closing this.