Hi All
I want to configure openshift container platform (3.10) with ipv6
networking.
Is it possible? if yes Can anybody send me the link how to do it.
Thanks
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com
Hi All
I want to configure openshift container platform with ipv6 networking.
Can anybody send me the link how to do it.
Thanks
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
project
calico for IPv6 support, I don't know if that applies to 3.7 or not, but
calico is quite a different network deployment though.
https://www.projectcalico.org/enable-ipv6-on-kubernetes-with-project-calico/
On Tue, Sep 25, 2018 at 11:46 AM Diego Armando Ramirez Avelino <
dramir...@ipn.mx>
IPv6 support for Openshift 3.7, is available?
Greetings
--
[cid:part1.3F43019E.7C042458@ipn.mx]
La informaci?n de este correo as? como la contenida en los documentos que se
adjuntan, pueden ser objeto de solicitudes de acceso a la informaci?n.
Vis?tanos: http
I am running OCP 3.7.54.
I can only find notes indicating IPv6 is not supported, but no indication in
the prereqs that it should be disabled on the nodes. In my case IPv6 is not
specifically configured so there are only link local addresses present. I
suspect it is causing me problems.
While
fine for
several months, but stopped working
yesterday. We
resolved
the issue
by using 127.0.0.1. We were also able to use
the pod
hostname
ubernetes-related, but thought I'd
>> ask here first.
>>
>> We have two containers running on a pod, and one container is
>> connecting to the other using 'localhost'. This has worked fine for
>> several months, but stopped working yesterday. We resolved the iss
ne container is
connecting to the other using 'localhost'. This has worked fine for
several months, but stopped working yesterday. We resolved the issue
by using 127.0.0.1. We were also able to use the pod hostname as well.
I'm thinking this might be related to IPv6, given that /etc/host
This has worked fine for several months,
> but stopped working yesterday. We resolved the issue by using 127.0.0.1. We
> were also able to use the pod hostname as well.
>
> I'm thinking this might be related to IPv6, given that /etc/hosts seemed
> to contain IPv6 records for local