Failed to Configure MetalLB on Baremetal
Quote from moshe on 02/08/2022, 10:42 pmProblem
After deployment of MetalLB manifest ( verified pods running )
trying to deploy a basic configuration
apiVersion: metallb.io/v1beta1
kind: IPAddressPool
metadata:
name: first-pool
namespace: metallb-system
spec:
addresses:
– 10.2.43.30-10.2.43.40user gets the following error
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
Solution
This error appears when trying to apply a configuration for IP address after having metallb installed or upgraded either default namespace or metallb-system namespace .
After long investigation on complicated setups metallb will not work along with caligo network provider.
My setup includes virtual machine control-plane and 3 baremetal on a different networking without identical hardware configuration for example ens192 on the VM and bond0 on the baremetal servers.
The solution that provides the option to automatically configure IP addresses for services / ingress is to configure weavenetworks / flannel networks along with OpenEIP additional details available here
OpenELB Installation
https://openelb.io/docs/getting-started/installation/
Use OpenELB in Layer 2 Mode
https://openelb.io/docs/getting-started/usage/use-openelb-in-layer-2-mode/
Problem
After deployment of MetalLB manifest ( verified pods running )
trying to deploy a basic configuration
apiVersion: metallb.io/v1beta1
kind: IPAddressPool
metadata:
name: first-pool
namespace: metallb-system
spec:
addresses:
– 10.2.43.30-10.2.43.40
user gets the following error
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
Solution
This error appears when trying to apply a configuration for IP address after having metallb installed or upgraded either default namespace or metallb-system namespace .
After long investigation on complicated setups metallb will not work along with caligo network provider.
My setup includes virtual machine control-plane and 3 baremetal on a different networking without identical hardware configuration for example ens192 on the VM and bond0 on the baremetal servers.
The solution that provides the option to automatically configure IP addresses for services / ingress is to configure weavenetworks / flannel networks along with OpenEIP additional details available here
OpenELB Installation
https://openelb.io/docs/getting-started/installation/
Use OpenELB in Layer 2 Mode
https://openelb.io/docs/getting-started/usage/use-openelb-in-layer-2-mode/
Uploaded files: