SpiderPool Controller Crash On k8s 1.29 (k0s installer)

Spiderpool Version
chart spiderpool-0.9.1
Bug Type
Installation Issue
Main CNI
kube-router
What happened?
Tried to install spiderpool using the following commands:
helm repo add spiderpool https://spidernet-io.github.io/spiderpool
helm repo update spiderpool
helm install spiderpool spiderpool/spiderpool --namespace kube-system --set ipam.enableStatefulSet=true

spirderpool controller pod keeps crashing with the following error logs:
kubectl get no -o wide
NAME                 STATUS   ROLES           AGE   VERSION       INTERNAL-IP      EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME
talos-mgmt-cluster   Ready    control-plane   32m   v1.29.1+k0s   <IP_ADDRESS>   <none>        Ubuntu 20.04.6 LTS   5.4.0-170-generic   containerd://1.7.13

kubectl -n kube-system get po
NAME                                     READY   STATUS             RESTARTS      AGE
kube-proxy-cgkfw                         1/1     Running            0             29m
kube-router-znjd5                        1/1     Running            0             29m
coredns-6cd46fb86c-wcrtl                 1/1     Running            0             29m
metrics-server-7556957bb7-6m97x          1/1     Running            0             29m
metallb-controller-648b76f565-ss79k      1/1     Running            0             17m
metallb-speaker-zrmxv                    4/4     Running            0             17m
spiderpool-agent-ktb4n                   1/1     Running            0             13m
multus-cni-whbrh                         1/1     Running            0             10m
spiderpool-init                          0/1     Error              0             13m
spiderpool-controller-786774fdc4-tq97q   0/1     CrashLoopBackOff   7 (64s ago)   13m

kubectl -n kube-system logs spiderpool-controller-786774fdc4-tq97q
{"level":"INFO","ts":"2024-02-07T00:34:13.014Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:57","msg":"CommitVersion: 32c8359256d008cbd73e04757f8085887de1aec2"}
{"level":"INFO","ts":"2024-02-07T00:34:13.014Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:60","msg":"CommitTime: 2024-01-29T17:37:04+08:00"}
{"level":"INFO","ts":"2024-02-07T00:34:13.014Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:63","msg":"AppVersion: v0.9.1"}
{"level":"INFO","ts":"2024-02-07T00:34:13.014Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:68","msg":"Default max golang procs: 8"}
{"level":"INFO","ts":"2024-02-07T00:34:13.014Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:78","msg":"Spiderpool-controller config: {CommitVersion:32c8359256d008cbd73e04757f8085887de1aec2 CommitTime:2024-01-29T17:37:04+08:00 AppVersion:v0.9.1 GoMaxProcs:8 ConfigPath:/tmp/spiderpool/config-map/conf.yml TlsServerCertPath:/etc/tls/tls.crt TlsServerKeyPath:/etc/tls/tls.key LogLevel:info EnableMetric:false EnableDebugLevelMetric:false MetricRenewPeriod:120 HttpPort:5720 MetricHttpPort:5721 WebhookPort:5722 GopsListenPort:5724 PyroscopeAddress: DefaultCniConfDir:/etc/cni/net.d CiliumConfigName:kube-system/cilium-config ControllerPodNamespace:kube-system ControllerPodName:spiderpool-controller-786774fdc4-tq97q LeaseDuration:15 LeaseRenewDeadline:10 LeaseRetryPeriod:2 LeaseRetryGap:1 IPPoolMaxAllocatedIPs:5000 SubnetInformerResyncPeriod:300 SubnetInformerWorkers:5 SubnetInformerMaxWorkqueueLength:10000 SubnetAppControllerWorkers:5 IPPoolInformerResyncPeriod:300 IPPoolInformerWorkers:3 IPPoolInformerMaxWorkQueueLength:10000 WorkQueueMaxRetries:500 WorkQueueRequeueDelayDuration:5 CoordinatorInformerResyncPeriod:60 EnableMultusConfig:true MultusConfigInformerResyncPeriod:60 EnableIPv4:true EnableIPv6:true EnableStatefulSet:true EnableKubevirtStaticIP:true EnableSpiderSubnet:true ClusterSubnetDefaultFlexibleIPNum:1}"}
{"level":"INFO","ts":"2024-02-07T00:34:13.066Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:91","msg":"gops is listening on <IP_ADDRESS>:5724"}
{"level":"INFO","ts":"2024-02-07T00:34:13.066Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:120","msg":"Begin to initialize spiderpool-controller metrics HTTP server"}
{"level":"INFO","ts":"2024-02-07T00:34:13.066Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:123","msg":"Begin to initialize spiderpool-controller runtime manager"}
{"level":"INFO","ts":"2024-02-07T00:34:13.075Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:255","msg":"Begin to initialize StatefulSet manager"}
{"level":"INFO","ts":"2024-02-07T00:34:13.075Z","logger":"Lease-Lock-Election","caller":"election/lease_election.go:163","msg":"'kube-system/spiderpool-controller-leases/spiderpool-controller-786774fdc4-tq97q' is trying to elect"}
I0207 00:34:13.075737       1 leaderelection.go:250] attempting to acquire leader lease kube-system/spiderpool-controller-leases...
{"level":"INFO","ts":"2024-02-07T00:34:13.076Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:151","msg":"Starting spiderpool-controller runtime manager"}
I0207 00:34:13.083544       1 leaderelection.go:260] successfully acquired lease kube-system/spiderpool-controller-leases
{"level":"INFO","ts":"2024-02-07T00:34:13.083Z","logger":"Lease-Lock-Election","caller":"election/lease_election.go:133","msg":"leader elected: kube-system/spiderpool-controller-leases/spiderpool-controller-786774fdc4-tq97q"}
{"level":"INFO","ts":"2024-02-07T00:34:13.177Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:161","msg":"Begin to initialize OpenAPI HTTP server"}
{"level":"INFO","ts":"2024-02-07T00:34:13.180Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:177","msg":"Begin to initialize IP GC Manager"}
{"level":"INFO","ts":"2024-02-07T00:34:13.181Z","logger":"spiderpool-controller","caller":"cmd/http_server.go:28","msg":"Serving spiderpool controller API at http://[[::]:5720]"}
{"level":"INFO","ts":"2024-02-07T00:34:13.182Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:180","msg":"Set spiderpool-controller Startup probe ready"}
{"level":"INFO","ts":"2024-02-07T00:34:13.183Z","logger":"IP-GarbageCollection","caller":"gcmanager/pod_informer.go:17","msg":"try to register pod informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.183Z","logger":"IP-GarbageCollection","caller":"gcmanager/gc_manager.go:160","msg":"running IP garbage collection"}
{"level":"INFO","ts":"2024-02-07T00:34:13.183Z","logger":"IP-GarbageCollection","caller":"gcmanager/pod_informer.go:49","msg":"create Pod informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.183Z","caller":"limiter/queue.go:135","msg":"Starting limiter"}
{"level":"INFO","ts":"2024-02-07T00:34:13.183Z","logger":"IP-GarbageCollection","caller":"gcmanager/tracePod_worker.go:74","msg":"Starting running 'releaseIPPoolIPExecutor'","IPPoolIP_Worker":1}
{"level":"INFO","ts":"2024-02-07T00:34:13.183Z","logger":"IP-GarbageCollection","caller":"gcmanager/tracePod_worker.go:74","msg":"Starting running 'releaseIPPoolIPExecutor'","IPPoolIP_Worker":3}
{"level":"INFO","ts":"2024-02-07T00:34:13.183Z","logger":"IP-GarbageCollection","caller":"gcmanager/scanAll_IPPool.go:58","msg":"receive CLI GC request, execute scan all right now!"}
{"level":"INFO","ts":"2024-02-07T00:34:13.183Z","logger":"IP-GarbageCollection","caller":"gcmanager/tracePod_worker.go:74","msg":"Starting running 'releaseIPPoolIPExecutor'","IPPoolIP_Worker":2}
{"level":"INFO","ts":"2024-02-07T00:34:13.183Z","logger":"IP-GarbageCollection","caller":"gcmanager/tracePod_worker.go:28","msg":"starting trace pod worker"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:461","msg":"Begin to set up Coordinator informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:474","msg":"Begin to set up IPPool informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"SpiderIPPool-Informer","caller":"ippoolmanager/ippool_informer.go:77","msg":"try to register SpiderIPPool informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:494","msg":"Begin to set up Subnet informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:507","msg":"Begin to set up auto-created IPPool controller"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"SpiderSubnet-Application-Controllers","caller":"applicationcontroller/app_controller.go:106","msg":"try to register SpiderSubnet App informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"spiderpool-controller","caller":"cmd/daemon.go:532","msg":"Begin to set up MultusConfig informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"SpiderIPPool-Informer","caller":"ippoolmanager/ippool_informer.go:109","msg":"create SpiderIPPool informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"MultusConfig-Informer","caller":"multuscniconfig/multusconfig_informer.go:73","msg":"try to register MultusConfig informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"MultusConfig-Informer","caller":"multuscniconfig/multusconfig_informer.go:105","msg":"create MultusConfig informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"Subnet-Informer","caller":"subnetmanager/subnet_informer.go:125","msg":"Initialize Dynamic informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"Coordinator-Informer","caller":"coordinatormanager/coordinator_informer.go:144","msg":"Initialize Coordinator informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"SpiderSubnet-Application-Controllers","caller":"applicationcontroller/app_controller.go:138","msg":"create SpiderSubnet App informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"Subnet-Informer","caller":"subnetmanager/subnet_informer.go:129","msg":"Initialize Subnet informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"SpiderSubnet-Application-Controllers","caller":"applicationinformers/deployment_informer.go:15","msg":"Setting up Deployment handlers"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"SpiderSubnet-Application-Controllers","caller":"applicationinformers/replicaset_informer.go:15","msg":"Setting up ReplicaSet handlers"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"SpiderSubnet-Application-Controllers","caller":"applicationinformers/statefulset_informer.go:15","msg":"Setting up StatefulSet handlers"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"SpiderSubnet-Application-Controllers","caller":"applicationinformers/daemonset_informer.go:15","msg":"Setting up DaemonSet handlers"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"SpiderSubnet-Application-Controllers","caller":"applicationinformers/job_informer.go:15","msg":"Setting up Job informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"SpiderSubnet-Application-Controllers","caller":"applicationinformers/cronjob_informer.go:15","msg":"Setting up CronJob handlers"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"Subnet-Informer","caller":"subnetmanager/subnet_informer.go:250","msg":"Starting Subnet informer"}
{"level":"INFO","ts":"2024-02-07T00:34:13.189Z","logger":"Subnet-Informer","caller":"subnetmanager/subnet_informer.go:252","msg":"Waiting for informer caches to sync"}
I0207 00:34:13.189663       1 shared_informer.go:311] Waiting for caches to sync for SpiderCoordinator
I0207 00:34:13.189900       1 shared_informer.go:311] Waiting for caches to sync for SpiderSubnet
I0207 00:34:13.290581       1 shared_informer.go:318] Caches are synced for SpiderSubnet
I0207 00:34:13.290743       1 shared_informer.go:318] Caches are synced for SpiderCoordinator
{"level":"INFO","ts":"2024-02-07T00:34:13.290Z","logger":"Subnet-Informer","caller":"subnetmanager/subnet_informer.go:257","msg":"Starting workers"}
{"level":"INFO","ts":"2024-02-07T00:34:13.290Z","logger":"Subnet-Informer","caller":"subnetmanager/subnet_informer.go:262","msg":"Starting dynamic informer worker"}
{"level":"INFO","ts":"2024-02-07T00:34:13.290Z","logger":"Subnet-Informer","caller":"subnetmanager/subnet_informer.go:265","msg":"Started workers"}
{"level":"INFO","ts":"2024-02-07T00:34:13.291Z","logger":"Coordinator-Informer","caller":"coordinatormanager/coordinator_informer.go:352","msg":"spidercoordinator change podCIDRType from auto to none","CoordinatorName":"default","Operation":"PROCESS"}
{"level":"WARN","ts":"2024-02-07T00:34:13.291Z","logger":"Coordinator-Informer","caller":"coordinatormanager/coordinator_informer.go:363","msg":"kube-system/kubeadm-config is no found, trying to fetch the ClusterCIDR from kube-controller-manager Pod","CoordinatorName":"default","Operation":"PROCESS"}
E0207 00:34:13.299179       1 runtime.go:79] Observed a panic: runtime.boundsError{x:0, y:0, signed:true, code:0x0} (runtime error: index out of range [0] with length 0)
goroutine 326 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic({0x2228240?, 0xc0006cfc68})
        /src/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:75 +0x99
k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0xc000035780?})
        /src/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:49 +0x75
panic({0x2228240, 0xc0006cfc68})
        /usr/local/go/src/runtime/panic.go:884 +0x213
github.com/spidernet-io/spiderpool/pkg/coordinatormanager.(*CoordinatorController).fetchPodAndServerCIDR(0xc00041a000, {0x2729bb8, 0xc0007a7500}, 0xc00059a380, 0xc001586000)
        /src/pkg/coordinatormanager/coordinator_informer.go:377 +0x9c6
github.com/spidernet-io/spiderpool/pkg/coordinatormanager.(*CoordinatorController).syncHandler(0xc00041a000, {0x2729bb8, 0xc0007a7500}, {0xc000336ec6, 0x7})
        /src/pkg/coordinatormanager/coordinator_informer.go:319 +0x17b
github.com/spidernet-io/spiderpool/pkg/coordinatormanager.(*CoordinatorController).processNextWorkItem(0xc00041a000, {0x2729bb8, 0xc0006c49f0})
        /src/pkg/coordinatormanager/coordinator_informer.go:292 +0x310
github.com/spidernet-io/spiderpool/pkg/coordinatormanager.(*CoordinatorController).runWorker(...)
        /src/pkg/coordinatormanager/coordinator_informer.go:276
k8s.io/apimachinery/pkg/util/wait.JitterUntilWithContext.func1()
        /src/vendor/k8s.io/apimachinery/pkg/util/wait/backoff.go:259 +0x25
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0x30?)
        /src/vendor/k8s.io/apimachinery/pkg/util/wait/backoff.go:226 +0x3e
k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0x1ec0120?, {0x2709ea0, 0xc0007a74a0}, 0x1, 0xc0006c6060)
        /src/vendor/k8s.io/apimachinery/pkg/util/wait/backoff.go:227 +0xb6
k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc0001b58f0?, 0x3b9aca00, 0x0, 0x0?, 0xc00011bef0?)
        /src/vendor/k8s.io/apimachinery/pkg/util/wait/backoff.go:204 +0x89
k8s.io/apimachinery/pkg/util/wait.JitterUntilWithContext({0x2729bb8, 0xc0006c49f0}, 0xc00011e950, 0xc00051f260?, 0xc00051f5f0?, 0x60?)
        /src/vendor/k8s.io/apimachinery/pkg/util/wait/backoff.go:259 +0x99
k8s.io/apimachinery/pkg/util/wait.UntilWithContext({0x2729bb8?, 0xc0006c49f0?}, 0xc000457c50?, 0xc000457e60?)
        /src/vendor/k8s.io/apimachinery/pkg/util/wait/backoff.go:170 +0x2b
created by github.com/spidernet-io/spiderpool/pkg/coordinatormanager.(*CoordinatorController).run
        /src/pkg/coordinatormanager/coordinator_informer.go:267 +0x170
panic: runtime error: index out of range [0] with length 0 [recovered]
        panic: runtime error: index out of range [0] with length 0

goroutine 326 [running]:
k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0xc000035780?})
        /src/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:56 +0xd7
panic({0x2228240, 0xc0006cfc68})
        /usr/local/go/src/runtime/panic.go:884 +0x213
github.com/spidernet-io/spiderpool/pkg/coordinatormanager.(*CoordinatorController).fetchPodAndServerCIDR(0xc00041a000, {0x2729bb8, 0xc0007a7500}, 0xc00059a380, 0xc001586000)
        /src/pkg/coordinatormanager/coordinator_informer.go:377 +0x9c6
github.com/spidernet-io/spiderpool/pkg/coordinatormanager.(*CoordinatorController).syncHandler(0xc00041a000, {0x2729bb8, 0xc0007a7500}, {0xc000336ec6, 0x7})
        /src/pkg/coordinatormanager/coordinator_informer.go:319 +0x17b
github.com/spidernet-io/spiderpool/pkg/coordinatormanager.(*CoordinatorController).processNextWorkItem(0xc00041a000, {0x2729bb8, 0xc0006c49f0})
        /src/pkg/coordinatormanager/coordinator_informer.go:292 +0x310
github.com/spidernet-io/spiderpool/pkg/coordinatormanager.(*CoordinatorController).runWorker(...)
        /src/pkg/coordinatormanager/coordinator_informer.go:276
k8s.io/apimachinery/pkg/util/wait.JitterUntilWithContext.func1()
        /src/vendor/k8s.io/apimachinery/pkg/util/wait/backoff.go:259 +0x25
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0x30?)
        /src/vendor/k8s.io/apimachinery/pkg/util/wait/backoff.go:226 +0x3e
k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0x1ec0120?, {0x2709ea0, 0xc0007a74a0}, 0x1, 0xc0006c6060)
        /src/vendor/k8s.io/apimachinery/pkg/util/wait/backoff.go:227 +0xb6
k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc0001b58f0?, 0x3b9aca00, 0x0, 0x0?, 0xc00011bef0?)
        /src/vendor/k8s.io/apimachinery/pkg/util/wait/backoff.go:204 +0x89
k8s.io/apimachinery/pkg/util/wait.JitterUntilWithContext({0x2729bb8, 0xc0006c49f0}, 0xc00011e950, 0xc00051f260?, 0xc00051f5f0?, 0x60?)
        /src/vendor/k8s.io/apimachinery/pkg/util/wait/backoff.go:259 +0x99
k8s.io/apimachinery/pkg/util/wait.UntilWithContext({0x2729bb8?, 0xc0006c49f0?}, 0xc000457c50?, 0xc000457e60?)
        /src/vendor/k8s.io/apimachinery/pkg/util/wait/backoff.go:170 +0x2b
created by github.com/spidernet-io/spiderpool/pkg/coordinatormanager.(*CoordinatorController).run
        /src/pkg/coordinatormanager/coordinator_informer.go:267 +0x170

What did you expect to happen?
All spiderpool pods should be up and running without crashes
How to reproduce it (as minimally and precisely as possible)

Install k8s cluster using k0s 1.29:

curl -sSLf https://get.k0s.sh | sudo sh
sudo k0s install controller --single
sudo k0s start
sudo k0s status

sudo k0s kubeconfig admin > ~/.kube/config

Install spiderpool

helm repo add spiderpool https://spidernet-io.github.io/spiderpool
helm repo update spiderpool
helm install spiderpool spiderpool/spiderpool --namespace kube-system --set ipam.enableStatefulSet=true

Additional Context
No response

Could you also show the logs of the spiderpool-init？ I think it is a bug, I will fix it later.

Looks like the spiderpool-init also depends on the controller been up:
kubectl -n kube-system logs spiderpool-init
{"level":"INFO","ts":"2024-02-07T00:27:31.072Z","logger":"Spiderpool-Init","caller":"cmd/config.go:211","msg":"Ignore creating default IPv4 Subnet or IPPool"}
{"level":"INFO","ts":"2024-02-07T00:27:31.072Z","logger":"Spiderpool-Init","caller":"cmd/config.go:250","msg":"Ignore creating default IPv6 Subnet or IPPool"}
{"level":"INFO","ts":"2024-02-07T00:27:31.072Z","logger":"Spiderpool-Init","caller":"cmd/config.go:301","msg":"Init default config: {Namespace:kube-system ControllerName:spiderpool-controller AgentName:spiderpool-agent CoordinatorName:default CoordinatorMode:auto CoordinatorPodCIDRType:auto CoordinatorPodDefaultRouteNic: CoordinatorPodMACPrefix: CoordinatorDetectGateway:false CoordinatorDetectIPConflict:false CoordinatorTunePodRoutes:true CoordinatorHijackCIDR:[<IP_ADDRESS>/16] V4SubnetName: V4IPPoolName: V4CIDR: V4IPRanges:[] V4Gateway: V6SubnetName: V6IPPoolName: V6CIDR: V6IPRanges:[] V6Gateway: enableMultusConfig:true installMultusCNI:true DefaultCNIDir:/etc/cni/net.d DefaultCNIName: DefaultCNINamespace:kube-system MultusConfigMap:spiderpool-multus ReadinessFile:/etc/spiderpool/ready}"}
{"level":"INFO","ts":"2024-02-07T00:27:31.169Z","logger":"Spiderpool-Init","caller":"cmd/root.go:38","msg":"Try to create default Coordinator default"}
{"level":"INFO","ts":"2024-02-07T00:27:32.182Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:27:35.190Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:27:38.198Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:27:41.206Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:27:44.214Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:27:47.226Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:27:50.262Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:27:53.270Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:27:56.278Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:27:59.286Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:02.294Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:05.302Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:08.310Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:11.318Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:14.326Z","caller":"cmd/client.go:68","msg":"Failed to create default Coordinator default, recreate in 2s: Internal error occurred: failed calling webhook \"spidercoordinator.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidercoordinator?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:16.344Z","caller":"cmd/client.go:54","msg":"Succeed to create default Coordinator: {TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:default GenerateName: Namespace: SelfLink: UID:caa98b8d-4e4f-45cb-bf43-ca9d5e27d296 ResourceVersion:1248 Generation:1 CreationTimestamp:2024-02-07 00:28:16 +0000 UTC DeletionTimestamp:<nil> DeletionGracePeriodSeconds:<nil> Labels:map[] Annotations:map[] OwnerReferences:[] Finalizers:[spiderpool.spidernet.io] ManagedFields:[{Manager:spiderpool-init Operation:Update APIVersion:spiderpool.spidernet.io/v2beta1 Time:2024-02-07 00:28:16 +0000 UTC FieldsType:FieldsV1 FieldsV1:{\"f:spec\":{\".\":{},\"f:detectGateway\":{},\"f:detectIPConflict\":{},\"f:hijackCIDR\":{},\"f:hostRPFilter\":{},\"f:hostRuleTable\":{},\"f:mode\":{},\"f:podCIDRType\":{},\"f:podDefaultRouteNIC\":{},\"f:podMACPrefix\":{},\"f:tunePodRoutes\":{},\"f:txQueueLen\":{}}} Subresource:}]} Spec:{Mode:0xc000199a40 PodCIDRType:0xc000199a50 HijackCIDR:[<IP_ADDRESS>/16] PodMACPrefix:0xc000199a70 TunePodRoutes:0xc0002a8f14 PodDefaultRouteNIC:0xc000199a60 HostRuleTable:0xc0002a8f00 HostRPFilter:0xc0002a8ee8 TxQueueLen:0xc0002a8f18 DetectIPConflict:0xc0002a8ee5 DetectGateway:0xc0002a8ee4} Status:{Phase: OverlayPodCIDR:[] ServiceCIDR:[]}}"}
{"level":"INFO","ts":"2024-02-07T00:28:16.344Z","logger":"Spiderpool-Init","caller":"cmd/config.go:314","msg":"the first cni config file is /etc/cni/net.d/10-kuberouter.conflist in /etc/cni/net.d"}
[controller-runtime] log.SetLogger(...) was never called; logs will not be displayed.
Detected at:
        >  goroutine 1 [running]:
        >  runtime/debug.Stack()
        >       /usr/local/go/src/runtime/debug/stack.go:24 +0x65
        >  sigs.k8s.io/controller-runtime/pkg/log.eventuallyFulfillRoot()
        >       /src/vendor/sigs.k8s.io/controller-runtime/pkg/log/log.go:60 +0xcd
        >  sigs.k8s.io/controller-runtime/pkg/log.(*delegatingLogSink).Enabled(0xc000135080, 0x4a00000000000000?)
        >       /src/vendor/sigs.k8s.io/controller-runtime/pkg/log/deleg.go:111 +0x3d
        >  github.com/go-logr/logr.Logger.Info({{0x1b23d48?, 0xc000135080?}, 0xc0003a2300?}, {0xc0003a2300, 0x93}, {0x0, 0x0, 0x0})
        >       /src/vendor/github.com/go-logr/logr/logr.go:280 +0x78
        >  sigs.k8s.io/controller-runtime/pkg/log.(*KubeAPIWarningLogger).HandleWarningHeader(0xc0005152f0?, 0x1?, {0x18af996?, 0x7?}, {0xc0003a2300?, 0x93?})
        >       /src/vendor/sigs.k8s.io/controller-runtime/pkg/log/warning_handler.go:65 +0x170
        >  k8s.io/client-go/rest.handleWarnings(0xc0003f6ea0?, {0x1b0b800?, 0xc0005152f0?})
        >       /src/vendor/k8s.io/client-go/rest/warnings.go:144 +0xfc
        >  k8s.io/client-go/rest.(*Request).transformResponse(0xc0001c2480, 0xc0001f6bd0, 0xc0001f4800)
        >       /src/vendor/k8s.io/client-go/rest/request.go:1179 +0x5cf
        >  k8s.io/client-go/rest.(*Request).Do.func1(0xc0002d09c0?, 0x0?)
        >       /src/vendor/k8s.io/client-go/rest/request.go:1064 +0x45
        >  k8s.io/client-go/rest.(*Request).request.func3.1(...)
        >       /src/vendor/k8s.io/client-go/rest/request.go:1039
        >  k8s.io/client-go/rest.(*Request).request.func3(0xc0001f6bd0, 0xc00056b2e0, {0x1b219b8?, 0xc0002d09c0?}, 0x0?, 0x0?, 0xc00056b278?, {0x0?, 0x0?}, 0x19aa508)
        >       /src/vendor/k8s.io/client-go/rest/request.go:1046 +0xde
        >  k8s.io/client-go/rest.(*Request).request(0xc0001c2480, {0x1b21440, 0xc00032b0e0}, 0x7?)
        >       /src/vendor/k8s.io/client-go/rest/request.go:1048 +0x4e5
        >  k8s.io/client-go/rest.(*Request).Do(0xc0001c2480, {0x1b21440, 0xc00032b0e0})
        >       /src/vendor/k8s.io/client-go/rest/request.go:1063 +0xc9
        >  sigs.k8s.io/controller-runtime/pkg/client.(*typedClient).Create(0xc0004b2900, {0x1b21440, 0xc00032b0e0}, {0x1b31c80?, 0xc00033fa40}, {0x0, 0x0, 0xc0003f4500?})
        >       /src/vendor/sigs.k8s.io/controller-runtime/pkg/client/typed_client.go:48 +0x366
        >  sigs.k8s.io/controller-runtime/pkg/client.(*client).Create(0xc0004b2900?, {0x1b21440?, 0xc00032b0e0?}, {0x1b31c80?, 0xc00033fa40?}, {0x0?, 0x0?, 0x0?})
        >       /src/vendor/sigs.k8s.io/controller-runtime/pkg/client/client.go:288 +0xf0
        >  github.com/spidernet-io/spiderpool/cmd/spiderpool-init/cmd.(*CoreClient).WaitForCoordinatorCreated(0xc0003eee20, {0x1b21440, 0xc00032b0e0}, 0xc00033fa40)
        >       /src/cmd/spiderpool-init/cmd/client.go:52 +0xef
        >  github.com/spidernet-io/spiderpool/cmd/spiderpool-init/cmd.Execute()
        >       /src/cmd/spiderpool-init/cmd/root.go:55 +0x446
        >  main.main()
        >       /src/cmd/spiderpool-init/main.go:11 +0x17
{"level":"INFO","ts":"2024-02-07T00:28:16.357Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": EOF"}
{"level":"INFO","ts":"2024-02-07T00:28:18.360Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:21.366Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:24.374Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:27.382Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:30.391Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:33.398Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:36.406Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:39.414Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:42.422Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:45.430Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:48.439Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:51.446Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:54.458Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:28:57.495Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:00.503Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:03.510Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:06.518Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:09.526Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:12.534Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:15.542Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:18.550Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:21.558Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:24.566Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:27.574Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:30.582Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:33.590Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:36.598Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:39.606Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:42.614Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:45.622Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:48.630Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:51.638Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:54.646Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:29:57.654Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:00.662Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:03.670Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:06.678Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:09.686Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:12.694Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:15.702Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:18.710Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:21.718Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:24.727Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:27.734Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:30.742Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:33.750Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:36.758Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:39.770Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:42.806Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:45.814Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:48.822Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:51.830Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:54.838Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:30:57.846Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:00.854Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:03.862Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:06.870Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:09.878Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:12.886Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:15.894Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:18.902Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:21.910Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:24.918Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:27.926Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:30.934Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:33.946Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:36.950Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:39.958Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:42.966Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:45.974Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:48.982Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:51.990Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:54.998Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:31:58.006Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:32:01.014Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:32:04.022Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:32:07.030Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:32:10.038Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:32:13.046Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:32:16.054Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:32:19.066Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:32:22.070Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:32:25.078Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"INFO","ts":"2024-02-07T00:32:28.086Z","caller":"cmd/client.go:178","msg":"Failed to create multuscniconfig kube-system/mynet, recreate in 2s: Internal error occurred: failed calling webhook \"spidermultusconfig.spiderpool.spidernet.io\": failed to call webhook: Post \"https://spiderpool-controller.kube-system.svc:5722/mutate-spiderpool-spidernet-io-v2beta1-spidermultusconfig?timeout=10s\": dial tcp <IP_ADDRESS>:5722: connect: connection refused"}
{"level":"FATAL","ts":"2024-02-07T00:32:31.073Z","logger":"Spiderpool-Init","caller":"cmd/root.go:152","msg":"context deadline exceeded"}

Hi using the latest release, the above error is not occurring but stateful pods are not coming up, following is the error from kubectl describe pod:
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason                  Age                  From               Message
  ----     ------                  ----                 ----               -------
  Normal   Scheduled               3m33s                default-scheduler  Successfully assigned default/test-sts-0 to k0s-spiderpool-test
  Warning  FailedCreatePodSandBox  3m33s                kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "d0b1b5d83ae644ee6b7d3cf841be8d3e86428c539c17250316af880c8243b662": plugin type="multus" name="multus-cni-network" failed (add): [default/test-sts-0/e6bdbf46-31b6-41e8-b2ef-04242d5cb212:macvlan-ens19]: error adding container to network "macvlan-ens19": failed to GetCoordinatorConfig: [GET /coordinator/config][500] getCoordinatorConfigFailure  spidercoordinator: default no ready
  Normal   SandboxChanged          6s (x17 over 3m32s)  kubelet            Pod sandbox changed, it will be killed and re-created.

The spider controller and agent pods are not giving any errors in the logs

Hi @infinitydon, Thanks for the report. Could you show some debug information using the following commands?
kubectl get spidercoordinator default -o yaml
kubectl get cm -n kube-system kubeadm-config -o yaml
kubectl get po -A -l component=kube-controller-manager

@cyclinder - I am currently using k0s and not kubeadm cluster, so kubectl get po -A -l component=kube-controller-manager and
kubectl get cm -n kube-system kubeadm-config -o yaml will not work for my cluster.
Is spider-pool made to work only in a kubeadm based cluster?
kubectl get spidercoordinator default -o yaml

apiVersion: spiderpool.spidernet.io/v2beta1
kind: SpiderCoordinator
metadata:
  creationTimestamp: "2024-03-07T15:44:21Z"
  finalizers:
  - spiderpool.spidernet.io
  generation: 1
  name: default
  resourceVersion: "662"
  uid: f86489c3-42a8-4b2c-afcd-b6cdfc239d11
spec:
  detectGateway: false
  detectIPConflict: false
  hijackCIDR:
  - <IP_ADDRESS>/16
  hostRPFilter: 0
  hostRuleTable: 500
  mode: auto
  podCIDRType: auto
  podDefaultRouteNIC: ""
  podMACPrefix: ""
  tunePodRoutes: true
  txQueueLen: 0
status:
  overlayPodCIDR: []
  phase: NotReady
  reason: No kube-controller-manager pod found, unable to get clusterCIDR
  serviceCIDR: []

Spiderpool-controller, this is just one replica:
kubectl -n kube-system get po
NAME                                    READY   STATUS      RESTARTS   AGE
kube-proxy-k5ptd                        1/1     Running     0          10h
kube-router-xx77q                       1/1     Running     0          10h
metrics-server-7556957bb7-dnjmr         1/1     Running     0          10h
coredns-6cd46fb86c-clh5d                1/1     Running     0          10h
spiderpool-controller-7c6f4fcdd-8ptlx   1/1     Running     0          10h
spiderpool-agent-zt6bp                  1/1     Running     0          10h
spiderpool-init                         0/1     Completed   0          10h

spiderpool-controller Logs attached below
spiderpool-logs-march-7-2024.txt

Is spider-pool made to work only in a kubeadm based cluster?

Currently, we synchronize the cluster CIDR from kubeadm-config configMap and KCM pod, I don't know much about k0s, can you tell me where I can get the cluster CIDR in a k0s based cluster?
And you can solve this by creating a configMap manually, please refer to https://spidernet-io.github.io/spiderpool/v0.9/usage/install/overlay/get-started-calico/#prerequisites.

Works now after creating the configmap.
For k0s, I am using the default settings, so the parameters can be retrieved from the k0s command k0s config create | grep -i cidr:
apiVersion: k0s.k0sproject.io/v1beta1
kind: ClusterConfig
metadata:
  creationTimestamp: null
  name: k0s
spec:
  api:
    address: <IP_ADDRESS>
    k0sApiPort: 9443
    port: 6443
    sans:
    - <IP_ADDRESS>
    - <IP_ADDRESS>
    - fe80::be24:11ff:fefb:7299
    - fe80::be24:11ff:fec3:394e
    - fe80::1005:ffff:fea5:39af
    - fe80::9416:34ff:fec4:6200
    - fe80::dccc:91ff:fe1e:e1d3
    - fe80::489b:6bff:fe1b:7417
    - fe80::3cb7:68ff:fe1e:72cb
    - fe80::3838:53ff:fe64:2c7a
  controllerManager: {}
  extensions:
    helm:
      charts: null
      concurrencyLevel: 5
      repositories: null
    storage:
      create_default_storage_class: false
      type: external_storage
  installConfig:
    users:
      etcdUser: etcd
      kineUser: kube-apiserver
      konnectivityUser: konnectivity-server
      kubeAPIserverUser: kube-apiserver
      kubeSchedulerUser: kube-scheduler
  konnectivity:
    adminPort: 8133
    agentPort: 8132
  network:
    calico: null
    clusterDomain: cluster.local
    dualStack: {}
    kubeProxy:
      iptables:
        minSyncPeriod: 0s
        syncPeriod: 0s
      ipvs:
        minSyncPeriod: 0s
        syncPeriod: 0s
        tcpFinTimeout: 0s
        tcpTimeout: 0s
        udpTimeout: 0s
      metricsBindAddress: <IP_ADDRESS>:10249
      mode: iptables
    kuberouter:
      autoMTU: true
      hairpin: Enabled
      ipMasq: false
      metricsPort: 8080
      mtu: 0
      peerRouterASNs: ""
      peerRouterIPs: ""
    nodeLocalLoadBalancing:
      envoyProxy:
        apiServerBindPort: 7443
        konnectivityServerBindPort: 7132
      type: EnvoyProxy
    podCIDR: <IP_ADDRESS>/16
    provider: kuberouter
    serviceCIDR: <IP_ADDRESS>/12
  scheduler: {}
  storage:
    etcd:
      externalCluster: null
      peerAddress: <IP_ADDRESS>
    type: etcd
  telemetry:
    enabled: true

Since spiderpool should be able to work on any k8s distro, I will suggest a different name for the configmap since not all the clusters will be based on kubeadm, maybe give it a generic name, what do you think?

Maybe we need a new ENV for spiderpool-controller, something like ClusterType. Its value can be kubeadm,k3s,k0s,systemd, etc. spiderpool-controller reads the value of this ENV at startup, and reads the cluster's CIDR from the relevant resources.
Can you read the ClusterConfig by using kubectl? like kubectl get clusterconfig -o yaml

kubectl get clusterconfig -o yaml does not work in the k0s:
ubuntu@k0s-spiderpool-test:~$ kubectl get clusterconfig -o yaml - clusterconfig
error: the server doesn't have a resource type "clusterconfig"

I agree with the suggestion of using ENV values so each user will be responsible for providing the values since there could be multiple ways of getting the values depending on the k8s distro.

Sadly, I went through on k0s quickly. Did not find a way to get cluster cidr by command or reading any resources, maybe we need to ask for help from the k0s community.

I think we can close issue for now, seems resolved from my side

I think we can close issue for now, seems resolved from my side

Happy pinging, how did you solve it ?


pull request for e2e test at 12/10/2016 06:56:02

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


API docs anchors on website works differently than on github

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Anchor links generated differently on github and website
For example on github we have
https://github.com/facebook/jest/blob/master/docs/API.md#tohavebeencalledwitharg1-arg2-
For website it will be
http://facebook.github.io/jest/docs/api.html#tohavebeencalledwith-arg1-arg2
What is the expected behavior?
Anchors working the same way for both sources

So with my PR https://github.com/facebook/jest/pull/1844 I was testing links on github and when it get merged website screw up. Will send PR to fix it tonight


Feature: different heights for progress-bars

Hello all!
I would like to propose you to define two new classes "progress-small" and "progress-large".
These classes, placed at the same element than the class "progress" is placed, will display a thinner progress-bar for class "progress-small" and a thicker progress-bar for class "progress-large"
Here is an example of HTML code used for a thinner bar:

        60%

And the same example but with a thicker bar:

        60%

To define these two classes, here is the LESS snippet I propose to you to place in progress-bars.less:
.progress {
  &.progress-small {
    height: @line-height-small-computed;
    margin-bottom: @line-height-small-computed;

    > .progress-bar {
      font-size: ceil((@font-size-small * 0.85));
      line-height: @line-height-small-computed;
    }
  }
  &.progress-large {
    height: @line-height-large-computed;
    margin-bottom: @line-height-large-computed;

    > .progress-bar {
      font-size: @font-size-base;
      line-height: @line-height-large-computed;
    }
  }
}

And here is the definition of the missing variables "@line-height-small-computed" and "@line-height-large-computed":
//== Typography (Extends)
//** Computed "line-height-small" (`font-size-small` * `line-height`) for use with progress-bars
@line-height-small-computed: floor((@font-size-small * @line-height-small)); // ~15px
//** Computed "line-height-large" (`font-size-large` * `line-height`) for use with progress-bars
@line-height-large-computed: floor((@font-size-large * @line-height-large)); // ~27px

I tested this also with text written into the progress-bar and both font-size and line-height seems correct to me.
Is this feature can be integrated on Bootstrap?
Thanks a lot,
Best regards,

Dupe of #16188. Thanks though!


why don't you use mcp over xds?

as we all know, istio 1.9 removed some mcp support

We have decided to directly create EnvoyFilters in K8s config store https://github.com/aeraki-framework/aeraki/pull/54 . This approach is preferred over mcp over xds because the generated EnvoyFilters are visible through Kubectl command tool, which is more convenient for users to figure out what changes has Aeraki done to the mesh.


Dec102023-ImplementingUni20-Inprogress

Hi @dipakmeher , thank you for your support of RecBole-CDR. Your commit has passed our test, but there seem to be some irrelevant output files. Could you please delete these irrelevant output files and commit again?

Thank you for the update. Which output file are you referring to? Is it the one below?
dcgm-gpu-stats-dgx001-1330040.out

I have deleted the irrelevant output and slurm files. Let me know if you need anything further from my end.


SQLite3: Enable execute() to run prepared_statements

Enable execute() to run prepared_statements for SQLite3.
Limit execute to run only non-select statements.
(Note: Does not apply to raw sql string select queries).

If you think that limiting execute() to running only non-select queries is a good idea, then I have another suggestion as well. Instead of using operator()() to run select queries, there should be a query() function.
Using query() then would signify that we expect returned (record) data while execute() would signify that we only want to run an operation where no records are returned. Similarly to RetT function(...) vs void method(...).
IMHO using operator() obfuscates the intent - and the resulting code - and should be deprecated (if that was available in C++11 - but why do we still stick to C++11?).
WDYT?

Thanks for the update. I forgot to ask for one more thing, sorry about the piece-meal review:
Can you add a test that uses the new form of execute?

Approved, thanks for the change!
Thanks for your offer to continue on this path:
MockDB: Indeed, just add the new version of execute and add a test to make sure this compiles.
MySQL and PostgreSQL: If you can't test this yourself, then I will do it. No problem.
query(): I am fine with query being the primary function.
Documentation: Awesome question :-) I am very open to suggestions.


Twitter module is also kinda broken

https://twitter.com/christruncer/status/515485410026594305
I'll dick around with this but I need someplace to keep notes until I have time to mess with it.

This seems to have fixed itself.
Ｑ Ｕ Ａ Ｌ Ｉ Ｔ Ｙ   Ｓ Ｏ Ｆ Ｔ Ｗ Ａ Ｒ Ｅ


Selectively capture the response body

It's about issue https://github.com/ariya/phantomjs/issues/10158

+1 this could be very cool to implement this feature

This would be very good to have, currently impossible to download attachments :(

This feature has been landed to master actually. See https://github.com/ariya/phantomjs/blob/master/src/webpage.h#L206

@Vitallium cool! Not sure that passing it as a string is such a good idea thought #13338


[Snyk] Security upgrade sanitize-html from 1.4.2 to 1.7.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json
package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

298/1000  Why? Confidentiality impact: High, Integrity impact: High, Availability impact: High, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): High, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00606, Social Trends: No, Days since published: 1066, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: Critical, Provider Urgency: High, Package Popularity Score: 99, Impact: 12.2, Likelihood: 2.43, Score Version: V5
Command Injection SNYK-JS-LODASH-1040724
No
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Command Injection

🎉 Snyk hasn't found any issues so far.
✅ security/snyk check is completed. No issues were found. (View Details)
✅ license/snyk check is completed. No issues were found. (View Details)


Ito hypomelanosis/ Nevus of Ito[Merge]

Mondo term (ID and Label)
Ito hypomelanosis MONDO:0010302
Reason for deprecation
Appears to be redundant with Nevus of Ito? NCI C7582 says these terms are synonyms; Mondo says both terms have "hypomelanosis of Ito" as exact synonyms. But is this correct? UMLS seems to take NCI's data and equate these terms on a single cui as well.

Term to be merged with
Nevus of Ito MONDO:0016985
Your nano-attribution (ORCID)
If you don't have an ORCID, you can sign up for one here

@kanems GARD treats these as two separate diseases, so let me check with them first.
@galyea-gard do you agree that these two terms should be merged? Thanks!

Emailed Gioconda on 11/29/21

From Gioconda:
We are going to review hipomelanosis of Ito (it was obsoleted from Orphanet); we may still keep the term because we do receive many inquiries about it but it does not represent a unique entity.  Regarding nevus of Ito I did see that NCI groups them as synonyms but they are different concepts.  Thank you! Gioconda

@kanems based on Gioconda's response, we think we should keep both terms in Mondo, as hypomelanosis of Ito is still being used by patients.
We made hypomelanosis of Ito a related synonym on 'nevus of Ito'.
Thanks!


Adding header text

Added text "Hello SHEros' & Hello World to the web page

Please specify which project your submitting and submit your pull request of that project correctly


Implementation of np.linalg.{cond, tensorinv}

Addresses #1999
This pull request implements np.linalg.cond - note that the testing has check_dtypes set to False as in some cases jax.numpy.linalg.norm will change the dtype to float32.
I've chucked the code in a new directory for third-party material and have put the numpy license in there seeing as this was a fairly straightforward port of their code. It gets imported into the correct namespace as is, though if more stuff was going to be added to that file it might be worth changing the __init__.py file to have an __all__ property so you could just import everything.
Please let me know if there's anything else needed for this pull request to be accepted, it was a lot of fun writing it up!

To better understand your test failures, please take a look at the docs on control flow: https://jax.readthedocs.io/en/latest/notebooks/Common_Gotchas_in_JAX.html#🔪-Control-Flow

To better understand your test failures, please take a look at the docs on control flow: https://jax.readthedocs.io/en/latest/notebooks/Common_Gotchas_in_JAX.html#🔪-Control-Flow

Thanks for this - I've re-written to eliminate if statements and the like from cond as suggested by that document. I'll get to tensorinv once that's sorted properly.
I've unfortunately hit a snag, though. The way the code is written now, I'm using jax.lax.cond to work out what to calculate for each p-norm value and then return that.
This has the effect of causing execution to fail, as jax.lax.cond passes an abstract value for the ord parameter of norm, which then hits an if statement inside jax.numpy.linalg.norm and falls over. norm tests the value of its parameter ord for obvious reasons; should this all be re-written using jax.lax.cond?
I'm not sure writing a different version of norm is really the answer here and don't really know what else I could do to try and sort this out. As things stand, norm passes the _CompileAndCheck test by using functools.partial to avoid this problem. In an effort to try and get away with this myself, one thing I thought of was currying jax.numpy.linalg.norm while I have access to the p-norm value and then passing that function into jax.lax.cond as an argument, but jax.lax.cond isn't happy with that:
TypeError: <class 'functools.partial'> is not a valid Jax type

I realise I've been bugging you a fair bit, sorry about this. As usual, any guidance would be appreciated.

This has the effect of causing execution to fail, as jax.lax.cond passes an abstract value for the ord parameter of norm, which then hits an if statement inside jax.numpy.linalg.norm and falls over. norm tests the value of its parameter ord for obvious reasons; should this all be re-written using jax.lax.cond?

It is fine some values like ord to use Python values like strings and not to be jit compatible -- array arguments are the ones that we need to be able to jit. Using closures and/or functools.partial within jit (or using jit's static_argnums parameter) is the typical way around this problem.

Ok, tests for both cond and tensorinv have a _CompileAndCheck now and the functions themselves have been re-written.

thanks @StephenHogg !

Thanks for accepting my contribution @shoyer !

Do we really need to create a third_party/numpy directory? This is creating some problems with the Google-internal source control. Why can't the cond be put in the existing numpy/linalg.py


deal with a data frame as the first element of inits

In assignDimensions if a user provides a data frame as the first element of inits we think that the user is in the mode of providing a list of lists rather than a list of variables.
Haven't thought this through thoroughly but initial thought is that we check that the first element is not a data frame in order to conclude that we are being given a list of lists.

Fixing this in branch no_df_init.


Enable your extension to run on VS Code for the web

Hello @HookyQR  👋
I'm part of the VS Code team and we recently launched VS Code for the web with github.dev! You can read the full guide for extension authors creating and migrating extensions here: Web Extensions

In hopes to help you migrate I helped make the changes necessary to make your extensions work on the web.
The changes I made:

Added webpack bundling to bundle your extension into 1 JavaScript file for the web
Added the compile scripts for webpack to your package.json
Added the necessary dependencies for bundling
Added the browser entry point to your package.json to link to the web-friendly compiled extension
Remove all extension uses of fs with the VS Code FileSystemProvider

Hi, Isidor here, a PM from VS Code 👋
We would really like to have VSCodeBeautify available in VS Code for Web.
@HookyQR  is there something blocking this PR from being merged? Can we help somehow with the PR review process?
Thanks a lot!

Hi, Isidor here, a PM from VS Code 👋 We would really like to have VSCodeBeautify available in VS Code for Web. @HookyQR is there something blocking this PR from being merged? Can we help somehow with the PR review process? Thanks a lot!

I think it's time to step up and fork this. A new release needs to come out.... Just about to cross 8 Million Install Count --- I posted #407 on Dec 21, 2021 -- and think it's time to circle back to this....

I have done so via the Slack initiative @vsce-toolroom :)

@tanhakabir thank you - your commit was cherry picked into https://marketplace.visualstudio.com/items?itemName=vsce-toolroom.vscode-beautify


refactor(FRE-880): increase API chains data usage

Fee assets, explorerUrl, pretty name now comes from API

I'm finding alot of the logic in use-swap-widget surprisingly difficult to follow, but as far as the refactor is concerned this looks good. The logic is definitely something I'll want to see if we can simplify in v2

I agree with you, it is difficult to follow. I'm avoiding to refactor this legacy code. Yes we need to simplify it in v2


textInputAction not available for keyboardType:TextInputType.number

Is there no possibility to display a done button (textInputAction: TextInputAction.done) for a number input (keyboardType: TextInputType.number)?

I just tried with current master and beta branch on an android device and was able to display the done button (Also tried with others like newLine)... in addition it is the default textInputAction used.
Could you please state which version you are using and attach a screenshot?

@Xavjer thanks!
Sorry I didn't test it on Android. The issue happens on iOS for me (emulator iPhone XS w/ iOS 12.0)
[✓] Flutter (Channel beta, v0.8.2, on Mac OS X 10.13.6 17G65, locale de-CH)
TextField(
        ...
        keyboardType: TextInputType.number,
        textInputAction: TextInputAction.done,
);

Okay then,
On iOS, the done action is not supported for number inputs, even in native applications.
In native applications, you would normally use an inputAccessoryView and add an UIToolBar to it, containing the done button. StackOverflow Link with this example
This widget does not exist yet for flutter, but is on the roadmap somewhere.
This is also an issue for multiline textFields, as you have no way to insert a newLine and having a done button at the same time.
For your purpose, it looks as if you have to enter a 6digit code, you can therefore:
a. Automatically continue when the last digit was entered.
b. Implement a gesture recognizer for a tab outside of the number keypad to close it
c. Write an own ToolBar that automatically pops-up when you open the number keypad

Thanks @Xavjer I just checked https://github.com/flutter/flutter/issues/12220 (sorry just saw it now)
I already implemented a.), but it would be nice to have a done button. Let's see when or if iOS will support this out-of-the-box.. 😄

This affects old android keyboards as well

Is there any update to this, i.e a roadmap of when/if InputAccessoryView  widget will be provided ? We have some screens whereby using Keyboard Actions plugin doesnt work and there is no way to have NEWLINE and ability to close the on screen keyboard. We cannot provide any gestures for the user to tap outside as on certain screens, there is just a series  multiline textfields which can grow depending on the content and thus no way to dismiss the keyboard ...

The https://pub.dartlang.org/packages/keyboard_actions is the best solution I have seen so far but the animation is janky.  Is there a way to have the view that contains the done button appear at the same rate and animation curve as the keyboard.  I would love to use this library but my skin crawls everyone time I see it.

I'm going to continue working on this package these days, anyway, PRs are open :)

This seems to be a duplicate of #12220

It does look like this is a duplicate of https://github.com/flutter/flutter/issues/12220. It looks like that one was closed because there's no way to do this in native iOS right now.


Deploy the support chart to meom-ige

This adds config for deploying the support chart for meom-ige
Enables prometheus authentication
Removes the LoadBalancer + autohttps config since we'll be using nginx-ingress

The following manual steps are required:

[x] deploy the support chart with:
python3 deployer deploy-support meom-ige
[x] retrieve the external IP address for the nginx-ingress load balancer.
kubectl --namespace support get svc support-ingress-nginx-controller
[x] point the dns record to this ip instead of proxy-public
[x] delete the proxy-public service
[x] do a deploy of the cluster
python3 deployer deploy meom-ige
[ ] merge this PR

@2i2c-org/tech-team, can you please confirm if the manual steps mentioned above ⬆ are ok please?
Ref: https://github.com/2i2c-org/infrastructure/issues/1278 and https://github.com/2i2c-org/infrastructure/issues/594

Manual steps also sound reasonable to me! 🙌🏻

@2i2c-org/tech-team, I believe I need some help debugging an issue during the support chart deploy.
The support-ingress-nginx-admission-create is hanging and I see this events:
 Normal   Scheduled               11m    gke.io/optimize-utilization-scheduler  Successfully assigned support/support-ingress-nginx-admission-create-xx5r7 to gke-meom-ige-cluster-core-pool-d987f2c6-jw1c
  Warning  FailedCreatePodSandBox  11m    kubelet                                Failed to create pod sandbox: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix /run/containerd/containerd.sock: connect: no such file or directory"
  Normal   Pulled                  8m17s  kubelet                                Container image "docker.io/jettech/kube-webhook-certgen:v1.5.1" already present on machine

@GeorgianaElena can you try deleting the pod and trying again? I've seen similar issues caused by race conditions go away on restart.

Deleted that pod then ran the deploy again and now I'm getting a x509: certificate signed by unknown authority
from validate.nginx.ingress.kubernetes.io

@GeorgianaElena delete all pods in the support cluster? 😁

Cattle not pets!

Cattle not pets!

Deleted all, then ran the deploy-support again and same error. I'm pasting its full text here:
Error: UPGRADE FAILED: cannot patch "support-prometheus-server" with kind Ingress: Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://support-ingress-nginx-controller-admission.support.svc:443/networking/v1beta1/ingresses?timeout=10s": x509: certificate signed by unknown authority
Traceback (most recent call last):

I'm keep seeing solutions online to delete the support-ingress-nginx-admission webhook. But there has to be a better way?

@GeorgianaElena if you delete the hook, helm should just recreate it next time, right? It's a job so might work ok.

Deleting the hook did the trick! I feel like I  still need to wrap my head around how first approach in solving something in k8s world, most of the times seem to be to delete things until they come up healthy and until a certain dependency order is achieved 🤯
Thanks a lot for the help @yuvipanda <3

For what it's worth @GeorgianaElena my strategy for debugging literally any issue in binder when we were first operating it was "Something wrong? Delete everything in kubernetes except for the helm installation" 😂

This is now done, so I'll merge it and then add this clustrer to the central grafana.

🚀 Thanks everybody