MicroK8s (Oracle Linux 9.5) & MetalLB Proxy Issues: Context Deadline Exceeded & Speaker CrashLoopBackOff - context deadline exceeded

Hi Everyone,

I’m seeking some assistance with a MicroK8s installation on an Oracle Linux Server 9.5. My goal is to use it with SC4SNMP for receiving SNMP traps.

My setup is behind a proxy, and I’ve configured the following environment variables: https_proxy, http_proxy, no_proxy, HTTP_PROXY, HTTPS_PROXY, NO_PROXY. These have also been added to the containerd-env file located at /var/snap/microk8s/current/args/.

However, I’m encountering issues when enabling MetalLB. Initially, I hit a “context deadline exceeded” error:

Error from server (InternalError): error when creating "STDIN": 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
Error from server (InternalError): error when creating "STDIN": 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
Failed to create default address pool, will retry

To bypass this, I tried setting the failurePolicy to Ignore, which allowed MetalLB to enable and create the address pools. However, now my MetalLB speakers are in a CrashLoopBackOff state, continuously restarting:

metallb-system   controller-5484c5f99f-sbkk9          1/1     Running              0           5d18h
metallb-system   speaker-4vb8v                        0/1     CrashLoopBackOff     2609 (3m1s ago)     5d18h
metallb-system   speaker-fpdtq                        0/1     Running              2612 (5m32s ago)    5d18h
metallb-system   speaker-vqkxp                        0/1     CrashLoopBackOff     2611 (3m1s ago)     5d18h

I’m suspecting this might be related to the proxy configuration. Apart from the environmental variables and containerd-env file, are there any other proxy-related settings I need to configure for MicroK8s or MetalLB to function correctly?

I also attempted a standalone installation, but the speaker pods still end up in CrashLoopBackOff.

Any suggestions or debug steps would be greatly appreciated!

Thanks in advance.