Thanks Jordan/Jason/Clayton for quick replies Good to knew that we can change port during provision time using ansible environment variables mentioned by Jason
However, this seems to be messy and confusing that user wont’ be able to change after the provision. At least too difficult unless all files across board reflect the new port Can we run a simple load balancer and listen on 443 and forward to all masters on port 8443. All the users will use standard vip:443. Openshift might create all kubeconfig files with 8443 reference. Can you validate above approach? It might ok to run load balance also on 8443 and forward to 8443 but am thinking clients should’t bother about always enter 8443 while connecting API or console The idea is run a simple load balancer for balancing multiple API masters. -- Srinivas Kotaru From: Jordan Liggitt <[email protected]<mailto:[email protected]>> Date: Wednesday, March 9, 2016 at 12:05 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Cc: skotaru <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: api and console port : 8443 also would need to adjust the port in the kubeconfig files used to connect to the master On Wed, Mar 9, 2016 at 3:03 PM, Clayton Coleman <[email protected]<mailto:[email protected]>> wrote: As long as you change the config, no. We chose 8443 in case you wanted to run a local TLS proxy, or in case you are running as a developer. On Wed, Mar 9, 2016 at 2:55 PM, Srinivas Naga Kotaru (skotaru) <[email protected]<mailto:[email protected]>> wrote: > Any reason why api and console exposed as 8443 rather 443? > > Any impact if we change 8443 to 443 by find and replace 8443 with 443 on > /etc/origin/master/master-config.yaml and restart master service? > > Do we need to change anything on node or etcd side? > > -- > Srinivas Kotaru > > _______________________________________________ > users mailing list > [email protected]<mailto:[email protected]> > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > _______________________________________________ users mailing list [email protected]<mailto:[email protected]> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
