Thanks for this step by step instructions Ryan's instructions were goog but not as good as this. Now the questions is how do I create a config file. I am new to OpenShift but enjoying my learning journy.
Good catch, you were still using the IPs Ryan's used. I have an issue in my cluster right now as I used "Cluster Managed Networking" but had the proxy server running on already. When I used "Cluster Managed Networking" it asked me for the IP address of api and *api, which I gave 192.168.22.5 and 192.168.22.10 so now the api is running on .5 address but I am not sure what that machine is since I never had that machine and but I can ping it. If you have any idea how to fix it please let me know otherwise I think I will have to rebuild the cluster again using "Customer Managed Network" just like you did.
You can use the load balancer IP allocated in OpenShift network. We use the same IP in DNS for all *api requests. In my case I have this IP in DNS and that is responsible to resolve the api dns record and all exposed applications with same domain. ; OpenShift Internal - Load balancer api.devopsvu.cluster1.local. IN A 10.10.10.1 api-int.devopsvu.cluster1.local. IN A 10.10.10.1 *.apps.devopsvu.cluster1.local. IN A 10.10.10.1
![4 DevOps Openshift Training [ NFS storage class setup using helm ]](http://i.ytimg.com/vi/zL0RICR6dCo/mqdefault.jpg)
![4 DevOps Openshift Training [ NFS storage class setup using helm ]](/img/tr.png)
![9 DevOps Openshift Training [ rsh to pod and generating ssl from cluster CA ]](http://i.ytimg.com/vi/QQPlDkuUKxQ/mqdefault.jpg)
![[LIVE] : ONE ลุมพินี 89 | คู่เอก "ยอดไอคิว vs คิริลล์"](http://i.ytimg.com/vi/Z3vYkHJ_5Ig/mqdefault.jpg)
![12 DevOps Openshift Training [ How does Templates works ]](/img/n.gif)
Thanks for this step by step instructions Ryan's instructions were goog but not as good as this. Now the questions is how do I create a config file. I am new to OpenShift but enjoying my learning journy.
Good catch, you were still using the IPs Ryan's used. I have an issue in my cluster right now as I used "Cluster Managed Networking" but had the proxy server running on already. When I used "Cluster Managed Networking" it asked me for the IP address of api and *api, which I gave 192.168.22.5 and 192.168.22.10 so now the api is running on .5 address but I am not sure what that machine is since I never had that machine and but I can ping it. If you have any idea how to fix it please let me know otherwise I think I will have to rebuild the cluster again using "Customer Managed Network" just like you did.
You can use the load balancer IP allocated in OpenShift network. We use the same IP in DNS for all *api requests. In my case I have this IP in DNS and that is responsible to resolve the api dns record and all exposed applications with same domain.
; OpenShift Internal - Load balancer
api.devopsvu.cluster1.local. IN A 10.10.10.1
api-int.devopsvu.cluster1.local. IN A 10.10.10.1
*.apps.devopsvu.cluster1.local. IN A 10.10.10.1