Description of problem:

This isn't a high priority problem, but we ran into it today and it's causing issues for us.

According to the RFC found here:

https://www.ietf.org/rfc/rfc1035.txt

a DNS "label" (I think I'm naming this correctly) can only have 63 characters in it.  IF it has more, DNS fails.  I believe the Openshift shouldn't allow users to have labels that are longer than 63 characters.  Here is further explanation.

If my dns name is:

<label1>.<label2>.<label3>

example:

foo.example.com

Each "label" can only have 63 chars.  More than that, dns fails to resolve.

In our case, we have this:

project name: ops-monitor-appbuildxxxxxx-xxxx-xxxx-xxxx-xxxxx
pod name in project:  nodejs-example

The output of "oc get route nodejs-example" -n ops-monitor-appbuildxxxxxx-xxxx-xxxx-xxxx-xxxxx" shows:

..<snip>..
spec:
    host: nodejs-example-ops-monitor-appbuildxxxxxx-xxxx-xxxx-xxxx-xxxxx.yyyy.zzzz.tttttt.com
..<snip>..

This host name is not valid and can not be resolved, so this is invalid.

Again, not a huge concern, but it is biting us.  This is a really long project name, so it's a unique situation, but we should be aware of it.

Version-Release number of selected component (if applicable):

atomic-openshift-3.1.1.6-6

How reproducible:

Very with long pod names and/or project names

Steps to Reproduce:
1.  create a really long project name
2.  create a really long pod name in the project created in #1
3.  try to resolve pod name

Actual results:

Dns will fail

Expected results:

Maybe Openshift shouldn't allow projects + pod to exceed 63 characters.