+1 decoupling application id and kub8 service name. What if we repeatedly query the existing service names and increment the seq no until an available service name is found? This is what we do when generating pod names.
On Thu, Sep 17, 2015 at 8:40 PM, Pubudu Gunatilaka <pubu...@wso2.com> wrote: > Hi Gayan, > > Can't we limit the Kubernetes service name rather than limiting the > application id. If we are deploying multiple applications, it would be > better if we can have meaningful name for the application ids. If we are > going to limit the kubernetes service name, we may have to come up with > another solution for that. We may not able to append the application id for > that. > > Thank you! > > On Thu, Sep 17, 2015 at 8:33 PM, Gayan Gunarathne <gay...@wso2.com> wrote: > >> Added the logic to validate the application ID length.This is because we >> are using the application ID as a Kubernetes service name which supports >> up-to 24 characters. >> >> But I could enable the application ID validation length to 20 as >> integration test are failed due to integration test samples application ID >> is greater than 20.Thus I set the max_length constant to 40 for the moment >> and push the changes to the Stratos-4.1.x. >> >> Will change the integration test samples with shorter application ID and >> will update the application ID max length to 20. >> >> Thanks, >> Gayan >> >> -- >> >> Gayan Gunarathne >> Technical Lead, WSO2 Inc. (http://wso2.com) >> Committer & PMC Member, Apache Stratos >> email : gay...@wso2.com | mobile : +94 775030545 <%2B94%20766819985> >> >> >> > > > > -- > > *Pubudu Gunatilaka* > Software Engineer > WSO2, Inc.: http://wso2.com > lean.enterprise.middleware > mobile: +94 77 4078049 > -- Akila Ravihansa Perera WSO2 Inc.; http://wso2.com/ Blog: http://ravihansa3000.blogspot.com
