I installed MetalLB using the following manifest:
kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.13.12/config/manifests/metallb-native.yaml
My cluster is configured in IPVS mode:
kubectl get configmap kube-proxy -n kube-system -o yaml |
sed -e "s/strictARP: false/strictARP: true/" |
kubectl diff -f - -n kube-system
However, when I try to install the following IPAddressPool:
apiVersion: metallb.io/v1beta1
kind: IPAddressPool
metadata:
name: address-pool
namespace: metallb-system
spec:
addresses:
- 192.168.1.1-192.168.1.254
---
apiVersion: metallb.io/v1beta1
kind: L2Advertisement
metadata:
name: l2advertisement
namespace: metallb-system
spec:
ipAddressPools:
- address-pool
Two webhooks seem to reject my configuration:
kubectl apply -f ipaddresspool.yaml
Error from server (InternalError): error when creating "ipaddresspool.yaml": Internal error occurred: failed calling webhook "l2advertisementvalidationwebhook.metallb.io": failed to call webhook: Post "https://webhook-service.metallb-system.svc:443/validate-metallb-io-v1beta1-l2advertisement?timeout=10s": context deadline exceeded
Error from server (InternalError): error when creating "ipaddresspool.yaml": Internal error occurred: failed calling webhook "ipaddresspoolvalidationwebhook.metallb.io": failed to call webhook: Post "https://webhook-service.metallb-system.svc:443/validate-metallb-io-v1beta1-ipaddresspool?timeout=10s": context deadline exceeded
Can you help me resolve this issue?
I tried the solution proposed in this issue, then the IP AddressPools install correctly, but the external IPs are only accessible internally. I cannot curl my external IP, for example, from my master node.
New contributor
Couim747 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.