EXTERNAL-IP <pending>

[adinemer]

Multi-container Pod example – sidecar container

My environment: Fedora 38, Docker-Desktop, and K3d. For the mentioned example, svc-sidecar could not get an external IP address. I googled the problem and most of what I found pointed to K3d not supporting the "service:LoadBalancer".

[nigelpoulton]

Hi @adinemer

There are two options in the book:

• For Docker Desktop and other local installs: kubectl apply -f sidecar-local.yml
• For clusters in the cloud: kubectl apply -f sidecar-cloud.yml

The option for local installations like yours creates a NodePort Service instead of a LoadBalancer. It sounds like may be you applied the file intended for cluster in the the cloud that creates the LoadBalancer Service?

[Cloufish]

Hi @nigelpoulton

I don't want to open the next issue
So the type: LoadBalancer is only supported on the cloud?

I'm reading the Chapter on the Deployments and deploying hello-world app
But when I use apply svc.yml (Which is supported on on-premise, right?) I cannot access the webpage (ERR_CONNECTION_REFUSED)

When I use:

$ k describe svc hello-svc
Name:                     hello-svc
Namespace:                default
Labels:                   app=hello-world
Annotations:              <none>
Selector:                 app=hello-world
Type:                     NodePort
IP Family Policy:         SingleStack
IP Families:              IPv4
IP:                       10.96.54.138
IPs:                      10.96.54.138
Port:                     <unset>  8080/TCP
TargetPort:               8080/TCP
NodePort:                 <unset>  30001/TCP
Endpoints:                10.244.2.3:8080,10.244.2.4:8080,10.244.2.5:8080 + 7 more...
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   <none>

I see Events:
Only when I specify in the .yml:

  externalIPs:
  - "192.168.x.x"
  - "192.168.x.y"
  - "192.167.x.z

I can reach my server
But somehow it is a lot slower to access these replicas