Requirement for load balancer

Paul Wright

unread,

Apr 21, 2021, 12:40:06 PM4/21/21

to Skupper

Hi,

I tried using skupper on a free IBM k8s cluster, however init never got past

Waiting for LoadBalancer IP or hostname...
Error: Failed to get LoadBalancer IP or Hostname for service skupper-router

I'm wondering if this relates to the fact that the free tier, ie a single node where they want you to use nodeport [1]

https://cloud.ibm.com/docs/containers?topic=containers-cs_troubleshoot_lb

Is there some requirement we're missing in docs?

I've deleted the site, but captured the debug if that helps,

Paul

--

Paul Wright

Technical Writer

Red Hat, Waterford, Ireland

GitHub: pwright

Paul Wright

unread,

Apr 21, 2021, 1:02:35 PM4/21/21

to Skupper

Ah, this is another enhancement request to 'add support for nodeport' [1]

as it's the only option for IBM free tier [2]

[1] https://groups.google.com/g/skupper/c/umO3cwpAOQs

[2] https://cloud.ibm.com/docs/containers?topic=containers-cs_network_planning

Paul

Gordon Sim

unread,

Apr 21, 2021, 4:03:13 PM4/21/21

to Paul Wright, Skupper

In step 9 of their getting started guide for the free tier they say:

"Return to the IBM Cloud clusters console, select your cluster,
and click the Worker Nodes tab. Find the Public IP of the worker node
that matches the private IP of the node that the pod runs on."

which I suspect means there is no way to get the public IP. Would
probably need that to be provided (as in the case Ted mentioned) for
use in conjunction with a nodeport.

Note that you can avoid the wait for init by specifying
--ingress=none. However no other site will be able to connect from
outside the cluster to that site. (That site can itself connect to
other sites though).

> --
> You received this message because you are subscribed to the Google Groups "Skupper" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to skupper+u...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/skupper/48cad67b-63a1-4372-b144-549793e07661n%40googlegroups.com.

Paul Wright

unread,

Apr 21, 2021, 4:14:04 PM4/21/21

to Skupper

Thanks Gordon,

I was able to deploy an nginx using nodeport and easily get the address (sent you the url privately)

The IP is temporary, so I'm not sure how useful this would be for anything other than short term use cases,

Paul

Gordon Sim

unread,

Apr 21, 2021, 4:19:34 PM4/21/21

to Paul Wright, Skupper

On Wed, Apr 21, 2021 at 9:14 PM Paul Wright <pwr...@redhat.com> wrote:
> I was able to deploy an nginx using nodeport and easily get the address (sent you the url privately)

Did you do that through their console? Or was it available via the kube api?

> The IP is temporary, so I'm not sure how useful this would be for anything other than short term use cases,

Yes, that does make it less likely you would want to connect in except
as a short term test.

Paul Wright

unread,

Apr 21, 2021, 4:29:13 PM4/21/21

to Gordon Sim, Skupper

On Wed, Apr 21, 2021 at 9:19 PM Gordon Sim <gs...@redhat.com> wrote:

On Wed, Apr 21, 2021 at 9:14 PM Paul Wright <pwr...@redhat.com> wrote:
> I was able to deploy an nginx using nodeport and easily get the address (sent you the url privately)

Did you do that through their console? Or was it available via the kube api?

https://cloud.ibm.com/docs/containers?topic=containers-nodeport

ibmcloud ks worker ls --cluster <cluster_name>

returns the public IP

Paul

> The IP is temporary, so I'm not sure how useful this would be for anything other than short term use cases,

Yes, that does make it less likely you would want to connect in except
as a short term test.

Reply all

Reply to author

Forward