Arjan Hulshoff

In terms of scalability, it would be a huge step forward in using SSIS. At the moment we have SSIS in an out-scaling configuration on VMs. Unfortunately, this does not...

Removing the duplicate entries seems to help. Once removed the issue cannot be recreated as k8s doesn't allow it. But this may happen more often as I already found 3...

At the moment, I cannot show the situation I have. But later today or tomorrow I will rebuild the cluster on my test environment. The thing I already can tell...

I have 3 services like below:  Here you can see that `eip.openelb.kubesphere.io/v1alpha1` is twice in the service. These services are created by helm charts. The charts used are: -...

As far as I have seen, only this one: `Warning add/update eip 11m (x160 over 39h) IPAM k8s-n-1: operation not permitted`. It looks like a permission error, but I have...

Could this be caused by Calico v3.24.5?

This is the full log of openelb-manager: ``` {"level":"info","ts":1669824332.9447937,"logger":"controller-runtime.builder","msg":"skip registering a mutating webhook, admission.Defaulter interface is not implemented","GVK":"network.kubesphere.io/v1alpha2, Kind=Eip"} {"level":"info","ts":1669824332.9448903,"logger":"controller-runtime.builder","msg":"Registering a validating webhook","GVK":"network.kubesphere.io/v1alpha2, Kind=Eip","path":"/validate-network-kubesphere-io-v1alpha2-eip"} {"level":"info","ts":1669824332.9449246,"logger":"controller-runtime.webhook","msg":"registering webhook","path":"/validate-network-kubesphere-io-v1alpha2-eip"} {"level":"info","ts":1669824332.9463913,"logger":"setup","msg":"registering webhooks to the...

Do you mean that on top of the helm charts, I have to take the steps described here: [https://openelb.io/docs/getting-started/usage/use-openelb-in-layer-2-mode/](https://openelb.io/docs/getting-started/usage/use-openelb-in-layer-2-mode/). Or you mean on the network interface itself, so adding the...

I have disabled ipv6 and set some arp things in sysctl by using the following in sysctl.conf: ``` net.bridge.bridge-nf-call-ip6tables=1 net.bridge.bridge-nf-call-iptables=1 net.ipv4.ip_forward=1 net.ipv6.conf.all.disable_ipv6=1 net.ipv6.conf.ens3.disable_ipv6=1 net.ipv6.conf.default.disable_ipv6=1 net.ipv4.conf.all.arp_ignore=1 net.ipv4.conf.ens3.arp_ignore=1 net.ipv4.conf.all.arp_announce=2 net.ipv4.conf.ens3.arp_announce=2 ``` I...

Setting `net.bridge.bridge-nf-call-arptables=0` in sysctl.conf does not help either.