Hi, External IPs relies on either: - some cloud integration, which would provision some kind of LoadBalancer, then the allocated IP would show back as our Services external IP - with bare-metal: some pre-configured subnet, a pool of IPs that may be allocated to those services (I didn't see this much documented yet in 4.X, you can find some details on 3.X docs, eg: https://docs.openshift.com/container-platform/3.4/dev_guide/expose_service/expose_internal_ip_service.html#defining_ip_range )
On CRC, you might not be able to do this. Regards. On Mon, Nov 18, 2019 at 2:17 AM Just Marvin < marvin.the.cynical.ro...@gmail.com> wrote: > Hi, > > > https://docs.openshift.com/container-platform/4.2/networking/configuring-ingress-cluster-traffic/configuring-ingress-cluster-traffic-service-external-ip.html#nw-creating-project-and-service_configuring-ingress-cluster-traffic-service-external-ip > . > > Step 4 seems like magic. When I do that on my local CRC install, I get > this: > > [zaphod@oc6010654212 Downloads]$ oc get svc -n openshift-ingress > NAME TYPE CLUSTER-IP EXTERNAL-IP > PORT(S) AGE > router-internal-default ClusterIP 172.30.165.244 <none> > 80/TCP,443/TCP,1936/TCP 18d > [zaphod@oc6010654212 Downloads]$ > > Which is what I would have expected to see. Where is that > "router-default" entry coming from? I've added an external ip to the crc > device, so I think I've met the pre-requisites. Whats the step that I'm > missing? > > Regards, > Marvin > _______________________________________________ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > -- Samuel Martín Moro {EPITECH.} 2011 "Nobody wants to say how this works. Maybe nobody knows ..." Xorg.conf(5)
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
