Failed to allocate IP

[raphael10-collab]

If I set the IP Address in the metallb config file to the Public Floating IP I bought from the Cloud infrastructure provider or the Public IP of the node :

apiVersion: metallb.io/v1beta1
kind: IPAddressPool
metadata:
  name: default
  namespace: metallb-system
spec:
  addresses:
  - aaa.aaa.aa.aaa-aaa.aaa.aa.aaa
  autoAssign: true
---
apiVersion: metallb.io/v1beta1
kind: L2Advertisement
metadata:
  name: default
  namespace: metallb-system
spec:
  ipAddressPools:
  - default

when I install ingress-nginx with helm, I get the error message: Failed to allocate IP :

(base) raphy@raohy:~/.talos/ingress-nginx$ helm upgrade --install ingress-nginx ingress-nginx \
>   --repo https://kubernetes.github.io/ingress-nginx \
>   --namespace ingress-nginx --create-namespace
Release "ingress-nginx" does not exist. Installing it now.

->:

(base) raphy@raohy:~/.talos/ingress-nginx$ helm upgrade --install ingress-nginx ingress-nginx \
>   --repo https://kubernetes.github.io/ingress-nginx \
>   --namespace ingress-nginx --create-namespace
Release "ingress-nginx" does not exist. Installing it now.
 ->
(base) raphy@raohy:~/.talos/ingress-nginx$ kubectl -n ingress-nginx describe service ingress-nginx-controller
Name:                     ingress-nginx-controller
Namespace:                ingress-nginx
Labels:                   app.kubernetes.io/component=controller
                          app.kubernetes.io/instance=ingress-nginx
                          app.kubernetes.io/managed-by=Helm
                          app.kubernetes.io/name=ingress-nginx
                          app.kubernetes.io/part-of=ingress-nginx
                          app.kubernetes.io/version=1.13.3
                          helm.sh/chart=ingress-nginx-4.13.3
Annotations:              meta.helm.sh/release-name: ingress-nginx
                          meta.helm.sh/release-namespace: ingress-nginx
Selector:                 app.kubernetes.io/component=controller,app.kubernetes.io/instance=ingress-nginx,app.kubernetes.io/name=ingress-nginx
Type:                     LoadBalancer
IP Family Policy:         SingleStack
IP Families:              IPv4
IP:                       bb.bbb.bbb.bbb
IPs:                      bb.bbb.bbb.bbb
LoadBalancer Ingress:     ee.e.ee.e (VIP)
Port:                     http  80/TCP
TargetPort:               http/TCP
NodePort:                 http  32646/TCP
Endpoints:                dd.ddd.d.dd:80
Port:                     https  443/TCP
TargetPort:               https/TCP
NodePort:                 https  30443/TCP
Endpoints:                dd.ddd.d.dd:443
Session Affinity:         None
External Traffic Policy:  Cluster
Internal Traffic Policy:  Cluster
Events:
  Type     Reason            Age                 From                Message
  ----     ------            ----                ----                -------
  Normal   ClearAssignment   70s (x25 over 73s)  metallb-controller  current IP for "ingress-nginx/ingress-nginx-controller" not allowed by config, will attempt for new IP assignment: ["10.0.10.1"] is not allowed in config
  Warning  AllocationFailed  70s (x25 over 73s)  metallb-controller  Failed to allocate IP for "ingress-nginx/ingress-nginx-controller": no available IPs

If I set in the Metallb Config file internal IP, an internal IP is assigned to ingress-nginx without any issues, but I do not get External IP for the LoadBalancer :

apiVersion: metallb.io/v1beta1
kind: IPAddressPool
metadata:
  name: default
  namespace: metallb-system
spec:
  addresses:
  - 192.168.10.0/24
  - 192.168.9.1-192.168.9.5
  autoAssign: true
---
apiVersion: metallb.io/v1beta1
kind: L2Advertisement
metadata:
  name: default
  namespace: metallb-system
spec:
  ipAddressPools:
  - default



(base) raphy@raohy:~/.talos/ingress-nginx$ helm upgrade --install ingress-nginx 
ingress-nginx \
>   --repo https://kubernetes.github.io/ingress-nginx \
>   --namespace ingress-nginx --create-namespace

-> :

(base) raphy@raohy:~/.talos/ingress-nginx$ kubectl -n ingress-nginx describe service ingress-nginx-controller
Name:                     ingress-nginx-controller
Namespace:                ingress-nginx
Labels:                   app.kubernetes.io/component=controller
                          app.kubernetes.io/instance=ingress-nginx
                          app.kubernetes.io/managed-by=Helm
                          app.kubernetes.io/name=ingress-nginx
                          app.kubernetes.io/part-of=ingress-nginx
                          app.kubernetes.io/version=1.13.3
                          helm.sh/chart=ingress-nginx-4.13.3
Annotations:              meta.helm.sh/release-name: ingress-nginx
                          meta.helm.sh/release-namespace: ingress-nginx
                          metallb.io/ip-allocated-from-pool: default
Selector:                 app.kubernetes.io/component=controller,app.kubernetes.io/instance=ingress-nginx,app.kubernetes.io/name=ingress-nginx
Type:                     LoadBalancer
IP Family Policy:         SingleStack
IP Families:              IPv4
IP:                       ff.ff.fff.ff
IPs:                      ff.ff.fff.ff
LoadBalancer Ingress:     10.0.10.1 (VIP)
Port:                     http  80/TCP
TargetPort:               http/TCP
NodePort:                 http  31780/TCP
Endpoints:                gg.ggg.gg.ggg:80
Port:                     https  443/TCP
TargetPort:               https/TCP
NodePort:                 https  32674/TCP
Endpoints:                gg.ggg.gg.ggg:443
Session Affinity:         None
External Traffic Policy:  Cluster
Internal Traffic Policy:  Cluster
Events:
  Type    Reason           Age                 From                Message
  ----    ------           ----                ----                -------
  Normal  ClearAssignment  84s (x13 over 85s)  metallb-controller  current IP for "ingress-nginx/ingress-nginx-controller" not allowed by config, will attempt for new IP assignment: ["hh.h.hh.h"] is not allowed in config
  Normal  IPAllocated      84s (x12 over 85s)  metallb-controller  Assigned IP ["192.168.10.1"]
  Normal  nodeAssigned     73s (x25 over 75s)  metallb-speaker     announcing from node "k8s-eu-1-worker-1" with protocol "layer2"

(base) raphy@raohy:~/.talos/ingress-nginx$ kubectl -n ingress-nginx get svc
NAME                                 TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx-controller             LoadBalancer   aa.aaa.aaa.aa   hh.h.hh.h    80:31780/TCP,443:32674/TCP   59s
ingress-nginx-controller-admission   ClusterIP      bb.bb.bbb.bbb   <none>        443/TCP                      59s```

Looking for ways to use a VIP as External IP for LoadBalancing, I've found this youtube video: https://www.youtube.com/watch?v=BfMGInHtFBc&t=21s

In the comments three years ago someone asked this question:
"Can i use VIP as LoadBalancer EXTERNAL-IP?"
getting this answer:
"Currently you cannot. EXTERNAL-IP is typical the cloud controller manager's job. We don't have a cloud controller for bare metal (yet?) but it could make sense if/when we do to do this."

So... my question is: how to set an External (Public) IP Address to make it available and at disposal to the LoadBalancer?
Are there any Talos Settings which prevent to use Public IP Address for the LoadBalancer?
If the output above is correct, how to connect to the LoadBalancer? I tried with curl -v hh.h.hh.h:80 where hh.h.hh.h is the External-IP indicated by kubectl-n ingres-nginx get svc.ingress-nginx-controllerand I tried with the endpoint indicated bykubectl -n ingress-nginx describe service ingress-nginx-controller : curl -v gg.ggg.gg.gg:443 but got Couldn't connect to server error message