We installed all the prereqs. Than took the internetaccess away from our master + node and we started the playbook. It crashes here.
Can someone tell us what we're doing wrong?
Thanks for your reply. Just the main goal we want to obtain is to keep our traffic from pod to pod (using routes, router, dns-wildcard) internal. So performing al this stuf on a private IP. Is that possible?
I just checked this blog: http://dustymabe.com/2016/12/
07/installing-an-openshift- origin-cluster-on-fedora-25- atomic-host-part-1/#comment- 42901
He is using public ip's + private ip's. Are the privates useful in this case?
We're able to use both and use and we can setup our own dns server but we don't want that our routes are going outside of our cluster. In public and than going back in the cluster.
So main goal: translations of routes through router should stay in the private network.
Is that possible?
Van: Frederic Giloux <fgiloux redhat com>
Verzonden: donderdag 8 december 2016 13:35:12
Aan: Den Cowboy
CC: users lists openshift redhat
Onderwerp: Re: Which openshift instances need a public IPFrédéricRegards,Hi Den,you may need internet connectivity. Public IPs is not a requirement for that (confer proxy and NAT). Another option is to install OpenShift disconnected. See: https://docs.openshift.com/
container-platform/3.3/. install_config/install/ disconnected_install.html
Also, editing etc/hosts is not enough. You will require a proper DNS server (dnsmasq for instance) as the containers don't use /etc/hosts of the host for name resolution.
On Thu, Dec 8, 2016 at 1:37 PM, Den Cowboy <dencowboy hotmail com> wrote:
We have our own Registry (like dockerhub) from where we can pull images. (the registry is in the same private network 192.168.25.x).
Now we're trying to install OpenShift (very basic: 1 master + 1 node) on 192.168.25.1 and 192.168.25.2.
We have experience with those installs but than we used public ip's.
We have SSH acces from our master to our node.
But: prereqs: you need ansible on the master, git, docker on master and node, ...
- So initially we need public ip's on our servers to install those prerequisitions?
- Do we need a public IP on every instance when we want to run the playbook? (it failed for resolving something to check ik yum-utils were installed).
- Is this a good solution?: (public IP and private on master and node). Install prereqs and execute playbook. So we have a cluster. After that deleting the public network and reexecuting the playbook with only private ip's (or only a public ip on the master). Will this work?
So as you can see we can use some input in using the setup.
We want that the traffic between our nodes goes internally. So we probably need our own DNS server for hosts, routing, wildcards. (initially we try to cover this in /etc/hosts).
If someone has experience with the setup of OpenShift where the communication over routes (through the router) happends internally (so no public wildcard). Please share some knowledge :).
users mailing list
users lists openshift redhat c
Senior Middleware Consultant
Red Hat GmbH
MesseTurm, Friedrich-Ebert-Anlage 49, 60308 Frankfurt am Main
Delivering value year after year
Red Hat ranks # 1 in value among software vendors
Red Hat GmbH, http://www.de.redhat.com/ Sitz: Grasbrunn,
Handelsregister: Amtsgericht München, HRB 153243
Geschäftsführer: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill