Support for IPv6 in openshift container platform
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/openshiftmm/listinfo/users
Support for IPv6 in openshift container platform 3.10
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
Re: IPv6
It looks like not, I found some references saying that Kubernetes has alpha support in 1.9 and some improvements in 1.10 https://github.com/kubernetes/kubernetes/issues/1443 https://github.com/kubernetes/kubernetes/issues/62822 I did find this article suggesting that you might be able to use 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> wrote: > IPv6 support for Openshift 3.7, is available? > > Greetings > -- > > -- > > 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://www.ipn.mx > ___ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
IPv6
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://www.ipn.mx ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
is it recommended to disable ipv6
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 investigating timeouts during container creation I noticed lots of messages like this: Jul 19 14:00:38 ose-prod-node-09.example.com kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 19 14:00:38 ose-prod-node-09.example.com kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready This is odd because I have no eth0 physical interface, ifcfg-eth0 file, or udev rules referencing it. [root@ose-prod-node-09 ~]# nmcli dev DEVICE TYPE STATE CONNECTION team0 team connected mlag docker0 bridge connected docker0 eno1ethernet connected team0-eno1 eno2ethernet connected team0-eno2 eno3ethernet disconnected -- eno4ethernet disconnected -- vxlan_sys_4789 vxlandisconnected -- eth0ethernet unmanaged -- veth00853eeaethernet unmanaged -- ... While looking at the system a couple hours later there was suddenly a second default route added with a lower metric that made the node unreachable. I wonder if this was caused by NetworkManager reacting to a change in the unexplained eth0 interface. Oddly, the default route points to the IP of the tun0 interface as next hop and is directed out this previously nonexistant eth0 interface: [root@ose-prod-node-09 ~]# ip route ls default via 10.1.11.1 dev eth0 <-- ! default via 203.0.113.254 dev team0 proto dhcp metric 350 10.1.0.0/16 dev tun0 scope link 10.1.11.0/24 dev eth0 proto kernel scope link src 10.1.11.196 203.0.113.0/24 dev team0 proto kernel scope link src 203.0.113.9 metric 350 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 172.30.0.0/16 dev tun0 224.0.0.0/4 dev eth0 [root@ose-prod-node-09 ~]# ip -4 -o a 1: loinet 127.0.0.1/8 scope host lo\ valid_lft forever preferred_lft forever 6: team0inet 203.0.113.9/24 brd 203.0.113.255 scope global noprefixroute dynamic team0\ valid_lft 70821sec preferred_lft 70821sec 11: docker0inet 172.17.0.1/16 scope global docker0\ valid_lft forever preferred_lft forever 13: tun0inet 10.1.11.1/24 brd 10.1.11.255 scope global tun0\ valid_lft forever preferred_lft forever 17845: eth0inet 10.1.11.196/24 brd 10.1.11.255 scope global eth0\ valid_lft forever preferred_lft forever < ! Any idea how or why this eth0 would have been created by NetworkManager? Could it be caused by IPv6 being enabled and triggering all those link state events? ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: Resolving localhost (IPv6 issue?)
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/hosts
seemed to contain IPv6 records for
localhost, and
the other
container may be listening on IPv4 only. I tried
disabling
it with
sysctl net.ipv6.conf.all.disable_ipv6=1 to
verify, but I
still saw
the same issue.
sh-4.3$ cat /etc/hosts
# Kubernetes-managed hosts file.
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
fe00::0 ip6-mcastprefix
fe00::1 ip6-allnodes
fe00::2 ip6-allrouters
172.17.0.6 controller-queue1-tnvav
--
Ulf Lilleengen
___
users mailing list
users@lists.openshift.redhat.com
<mailto:users@lists.openshift.redhat.com>
<mailto:users@lists.openshift.redhat.com
<mailto:users@lists.openshift.redhat.com>>
<mailto:users@lists.openshift.redhat.com
<mailto:users@lists.openshift.redhat.com>
<mailto:users@lists.openshift.redhat.com
<mailto:users@lists.openshift.redhat.com>>>
<mailto:users@lists.openshift.redhat.com
<mailto:users@lists.openshift.redhat.com>
<mailto:users@lists.openshift.redhat.com
<mailto:users@lists.openshift.redhat.com>>
<mailto:users@lists.openshift.redhat.com
<mailto:users@lists.openshift.redhat.com>
<mailto:users@lists.openshift.redhat.com
<mailto:users@lists.openshift.redhat.com>>>>
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users>
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users>>
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users>
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users>>>
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users>
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users>>
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users>
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users>>>>
--
Ulf
--
Ulf
--
Ulf
--
Ulf
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: Resolving localhost (IPv6 issue?)
Tried this with Fedora 24 and very similar config (but centos7 image) and I'm able to ping localhost. $ cat /etc/hosts # Kubernetes-managed hosts file. 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet fe00::0 ip6-mcastprefix fe00::1 ip6-allnodes fe00::2 ip6-allrouters 172.17.0.2 centoscentos7-debug I have net.ipv6.conf.all.disable_ipv6 = 1 set - should be possible. Can you provide your /etc/resolv.conf from inside that image? On Thu, Aug 11, 2016 at 11:29 AM, Ulf Lilleengen <l...@redhat.com> wrote: > Host: > OS: Fedora 24 > Docker: 1.10.3 > glibc-2.23.1-8 > > Docker image: > Name: gordons/qdrouterd:v10 (based on Fedora 23) > Glibc:glibc-2.22-11 > > Nothing special in the images other than that. The issue appeared without > any significant change other than running the latest openshift/origin image. > > On 08/11/2016 04:58 PM, Clayton Coleman wrote: > >> That is very strange. Anything special about the container (what OS, >> libraries, glibc version, musl)? What version of Docker was running? >> >> On Wed, Aug 10, 2016 at 3:45 AM, Ulf Lilleengen <l...@redhat.com >> <mailto:l...@redhat.com>> wrote: >> >> Hi, >> >> We were debugging an issue yesterday where 'localhost' could not be >> resolved inside a container in openshift origin v1.3.0-alpha.3. I'm >> not sure if this is openshift or kubernetes-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 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 localhost, and the other >> container may be listening on IPv4 only. I tried disabling it with >> sysctl net.ipv6.conf.all.disable_ipv6=1 to verify, but I still saw >> the same issue. >> >> sh-4.3$ cat /etc/hosts >> # Kubernetes-managed hosts file. >> 127.0.0.1 localhost >> ::1 localhost ip6-localhost ip6-loopback >> fe00::0 ip6-localnet >> fe00::0 ip6-mcastprefix >> fe00::1 ip6-allnodes >> fe00::2 ip6-allrouters >> 172.17.0.6 controller-queue1-tnvav >> >> -- >> Ulf Lilleengen >> >> ___ >> users mailing list >> users@lists.openshift.redhat.com >> <mailto:users@lists.openshift.redhat.com> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> <http://lists.openshift.redhat.com/openshiftmm/listinfo/users> >> >> >> > -- > Ulf > ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: Resolving localhost (IPv6 issue?)
Host: OS: Fedora 24 Docker: 1.10.3 glibc-2.23.1-8 Docker image: Name: gordons/qdrouterd:v10 (based on Fedora 23) Glibc:glibc-2.22-11 Nothing special in the images other than that. The issue appeared without any significant change other than running the latest openshift/origin image. On 08/11/2016 04:58 PM, Clayton Coleman wrote: That is very strange. Anything special about the container (what OS, libraries, glibc version, musl)? What version of Docker was running? On Wed, Aug 10, 2016 at 3:45 AM, Ulf Lilleengen <l...@redhat.com <mailto:l...@redhat.com>> wrote: Hi, We were debugging an issue yesterday where 'localhost' could not be resolved inside a container in openshift origin v1.3.0-alpha.3. I'm not sure if this is openshift or kubernetes-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 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 localhost, and the other container may be listening on IPv4 only. I tried disabling it with sysctl net.ipv6.conf.all.disable_ipv6=1 to verify, but I still saw the same issue. sh-4.3$ cat /etc/hosts # Kubernetes-managed hosts file. 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet fe00::0 ip6-mcastprefix fe00::1 ip6-allnodes fe00::2 ip6-allrouters 172.17.0.6 controller-queue1-tnvav -- Ulf Lilleengen ___ users mailing list users@lists.openshift.redhat.com <mailto:users@lists.openshift.redhat.com> http://lists.openshift.redhat.com/openshiftmm/listinfo/users <http://lists.openshift.redhat.com/openshiftmm/listinfo/users> -- Ulf ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: Resolving localhost (IPv6 issue?)
That is very strange. Anything special about the container (what OS, libraries, glibc version, musl)? What version of Docker was running? On Wed, Aug 10, 2016 at 3:45 AM, Ulf Lilleengen <l...@redhat.com> wrote: > Hi, > > We were debugging an issue yesterday where 'localhost' could not be > resolved inside a container in openshift origin v1.3.0-alpha.3. I'm not > sure if this is openshift or kubernetes-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 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 localhost, and the other container may be > listening on IPv4 only. I tried disabling it with sysctl > net.ipv6.conf.all.disable_ipv6=1 to verify, but I still saw the same > issue. > > sh-4.3$ cat /etc/hosts > # Kubernetes-managed hosts file. > 127.0.0.1 localhost > ::1 localhost ip6-localhost ip6-loopback > fe00::0 ip6-localnet > fe00::0 ip6-mcastprefix > fe00::1 ip6-allnodes > fe00::2 ip6-allrouters > 172.17.0.6 controller-queue1-tnvav > > -- > Ulf Lilleengen > > ___ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
