Use an elastic IP address for your server. That way the address won't
change after a restart.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html
On 29/05/18 20:25, Iftikharuddin Khan wrote:
We have openshift running on an EC2 in AWS. We have the following
commands to bring the cluster up
/metadata_endpoint="http://169.254.169.254/latest/meta-data"/
/public_hostname="$( curl "${metadata_endpoint}/public-hostname" )"/
/public_ip="$( curl "${metadata_endpoint}/public-ipv4" )"/
/oc cluster up --public-hostname="${public_hostname}"
--routing-suffix="${public_ip}.nip.io"
--host-data-dir="/home/centos/oc_dir"/
It works fine as long as the EC2 is up. Once we stop the EC2 instance
and start it, the IP address of EC2 instance changes and because of
that somehow openshift is getting impacted. We can see the docker
containers running, but we cannot access the console. What should we
do to resolve it?
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
