Deployment of k3s cluster fails

Deployment of k3s cluster fails with following multiple errors:
Version v1.27.10-rc1+k3s1:

Local (deployment) machine log output:

`hetzner-k3s create --config vito_botta_test_cluster_config.yaml
Validating configuration......configuration seems valid.
=== Creating infrastructure resources ===
Creating network...done.
Creating firewall...done.
Creating SSH key...done.
Creating placement group test-masters...done.
Creating placement group test-small-static-1...done.
Creating server test-cx22-pool-small-static-worker1...
Creating server test-cx22-master1...
...server test-cx22-master1 created.
...server test-cx22-pool-small-static-worker1 created.
Server test-cx22-master1 already exists, skipping.
Waiting for successful ssh connectivity with server test-cx22-master1...
Server test-cx22-pool-small-static-worker1 already exists, skipping.
Waiting for successful ssh connectivity with server test-cx22-pool-small-static-worker1...
...server test-cx22-master1 is now up.
...server test-cx22-pool-small-static-worker1 is now up.
=== Setting up Kubernetes ===
Deploying k3s to first master test-cx22-master1...
[INFO]  Using v1.27.10+k3s2 as release
[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.27.10+k3s2/sha256sum-amd64.txt
[INFO]  Downloading binary https://github.com/k3s-io/k3s/releases/download/v1.27.10+k3s2/k3s
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
[INFO]  Skipping installation of SELinux RPM
[INFO]  Creating /usr/local/bin/kubectl symlink to k3s
[INFO]  Creating /usr/local/bin/crictl symlink to k3s
[INFO]  Creating /usr/local/bin/ctr symlink to k3s
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s.service
[INFO]  systemd: Enabling k3s unit
[INFO]  systemd: Starting k3s
Waiting for the control plane to be ready...
Saving the kubeconfig file to test_project/kubeconfig...
...k3s has been deployed to first master test-cx22-master1 and the control plane is up.
Deploying k3s to worker test-cx22-pool-small-static-worker1...
[INFO]  Using v1.27.10+k3s2 as release
[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.27.10+k3s2/sha256sum-amd64.txt
[INFO]  Downloading binary https://github.com/k3s-io/k3s/releases/download/v1.27.10+k3s2/k3s
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
[INFO]  Skipping installation of SELinux RPM
[INFO]  Creating /usr/local/bin/kubectl symlink to k3s
[INFO]  Creating /usr/local/bin/crictl symlink to k3s
[INFO]  Creating /usr/local/bin/ctr symlink to k3s
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-agent-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s-agent.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s-agent.service
[INFO]  systemd: Enabling k3s-agent unit
[INFO]  systemd: Starting k3s-agent
...k3s has been deployed to worker test-cx22-pool-small-static-worker1.
=== Deploying Hetzner drivers ===
Creating secret for Hetzner Cloud token...
error: error validating "STDIN": error validating data: failed to download openapi: Get "https://<IP_ADDRESS>:6443/openapi/v2?timeout=32s": dial tcp <IP_ADDRESS>:6443: connect: connection refused; if you choose to ignore these errors, turn validation off with --validate=false
Failed to create Hetzner Cloud secret:
#Util::Shell::Result:0x10fd40300
`

Syslog from worker node (k3s-agent):

Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.594357    2966 kube.go:489] Starting kube subnet manager Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.595211    2966 server.go:657] "--cgroups-per-qos enabled, but --cgroup-root was not specified.  defaulting to /" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.595751    2966 container_manager_linux.go:265] "Container manager verified user specified cgroup-root exists" cgroupRoot=[] Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.595858    2966 container_manager_linux.go:270] "Creating Container Manager object based on Node Config" nodeConfig={RuntimeCgroupsName: SystemCgroupsName: KubeletCgroupsName: KubeletOOMScoreAdj:-999 ContainerRuntime: CgroupsPerQOS:true CgroupRoot:/ CgroupDriver:systemd KubeletRootDir:/var/lib/kubelet ProtectKernelDefaults:false NodeAllocatableConfig:{KubeReservedCgroupName: SystemReservedCgroupName: ReservedSystemCPUs: EnforceNodeAllocatable:map[pods:{}] KubeReserved:map[] SystemReserved:map[] HardEvictionThresholds:[{Signal:imagefs.available Operator:LessThan Value:{Quantity:<nil> Percentage:0.05} GracePeriod:0s MinReclaim:<nil>} {Signal:nodefs.available Operator:LessThan Value:{Quantity:<nil> Percentage:0.05} GracePeriod:0s MinReclaim:<nil>}]} QOSReserved:map[] CPUManagerPolicy:none CPUManagerPolicyOptions:map[] TopologyManagerScope:container CPUManagerReconcilePeriod:10s ExperimentalMemoryManagerPolicy:None ExperimentalMemoryManagerReservedMemory:[] PodPidsLimit:-1 EnforceCPULimits:true CPUCFSQuotaPeriod:100ms TopologyManagerPolicy:none ExperimentalTopologyManagerPolicyOptions:map[]} Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.595906    2966 topology_manager.go:136] "Creating topology manager with policy per scope" topologyPolicyName="none" topologyScopeName="container" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.595939    2966 container_manager_linux.go:301] "Creating device plugin manager" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.596025    2966 state_mem.go:36] "Initialized new in-memory state store" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.599325    2966 kubelet.go:405] "Attempting to sync node with API server" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.599571    2966 kubelet.go:298] "Adding static pod path" path="/var/lib/rancher/k3s/agent/pod-manifests" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.599809    2966 kubelet.go:309] "Adding apiserver pod source" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.600240    2966 apiserver.go:42] "Waiting for node sync before watching apiserver pods" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.603922    2966 kuberuntime_manager.go:257] "Container runtime initialized" containerRuntime="containerd" version="v1.7.11-k3s2.27" apiVersion="v1" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.604357    2966 kube.go:510] Creating the node lease for IPv4. This is the n.Spec.PodCIDRs: [<IP_ADDRESS>/24] Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.604539    2966 kube.go:510] Creating the node lease for IPv4. This is the n.Spec.PodCIDRs: [<IP_ADDRESS>/24] Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.604786    2966 server.go:1163] "Started kubelet" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: E0801 19:23:15.606408    2966 cri_stats_provider.go:455] "Failed to get the info of the filesystem with mountpoint" err="unable to find data in memory cache" mountpoint="/var/lib/rancher/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: E0801 19:23:15.606627    2966 kubelet.go:1400] "Image garbage collection failed once. Stats initialization may not have completed yet" err="invalid capacity 0 on image filesystem" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.606998    2966 fs_resource_analyzer.go:67] "Starting FS ResourceAnalyzer" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.611634    2966 server.go:162] "Starting to listen" address="<IP_ADDRESS>" port=10250 Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.612809    2966 server.go:461] "Adding debug handlers to kubelet server" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.614159    2966 ratelimit.go:65] "Setting rate limiting for podresources endpoint" qps=100 burstTokens=10 Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.615083    2966 volume_manager.go:284] "Starting Kubelet Volume Manager" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.617832    2966 desired_state_of_world_populator.go:145] "Desired state populator starts to run" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.621169    2966 kubelet_network_linux.go:63] "Initialized iptables rules." protocol=IPv4 Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.622573    2966 kubelet_network_linux.go:63] "Initialized iptables rules." protocol=IPv6 Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.622599    2966 status_manager.go:207] "Starting to sync pod status with apiserver" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.622623    2966 kubelet.go:2257] "Starting kubelet main sync loop" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: E0801 19:23:15.622697    2966 kubelet.go:2281] "Skipping pod synchronization" err="[container runtime status check may not have completed yet, PLEG is not healthy: pleg has yet to be successful]" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.644143    2966 cpu_manager.go:214] "Starting CPU manager" policy="none" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.644424    2966 cpu_manager.go:215] "Reconciling" reconcilePeriod="10s" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.644557    2966 state_mem.go:36] "Initialized new in-memory state store" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.644912    2966 state_mem.go:88] "Updated default CPUSet" cpuSet="" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.645082    2966 state_mem.go:96] "Updated CPUSet assignments" assignments=map[] Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.645210    2966 policy_none.go:49] "None policy: Start" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.646007    2966 memory_manager.go:169] "Starting memorymanager" policy="None" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.646159    2966 state_mem.go:35] "Initializing new in-memory state store" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.646491    2966 state_mem.go:75] "Updated machine memory state" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.655291    2966 manager.go:471] "Failed to read data from checkpoint" checkpoint="kubelet_internal_checkpoint" err="checkpoint is not found" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.655872    2966 plugin_manager.go:118] "Starting Kubelet Plugin Manager" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.717998    2966 kubelet_node_status.go:70] "Attempting to register node" node="test-cx22-pool-small-static-worker1" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.746684    2966 kubelet_node_status.go:108] "Node was previously registered" node="test-cx22-pool-small-static-worker1" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.746940    2966 kubelet_node_status.go:73] "Successfully registered node" node="test-cx22-pool-small-static-worker1" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.749536    2966 kuberuntime_manager.go:1460] "Updating runtime config through cri with podcidr" CIDR="<IP_ADDRESS>/24" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.750910    2966 kubelet_network.go:61] "Updating Pod CIDR" originalPodCIDR="" newPodCIDR="<IP_ADDRESS>/24" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:23:15Z" level=info msg="Running kube-proxy --cluster-cidr=<IP_ADDRESS>/16 --conntrack-max-per-core=0 --conntrack-tcp-timeout-close-wait=0s --conntrack-tcp-timeout-established=0s --healthz-bind-address=<IP_ADDRESS> --hostname-override=test-cx22-pool-small-static-worker1 --kubeconfig=/var/lib/rancher/k3s/agent/kubeproxy.kubeconfig --proxy-mode=iptables" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.872410    2966 server.go:226] "Warning, all flags other than --config, --write-config-to, and --cleanup are deprecated, please begin using a config file ASAP" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.896843    2966 node.go:141] Successfully retrieved node IP: <IP_ADDRESS> Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.896892    2966 server_others.go:110] "Detected node IP" address="<IP_ADDRESS>" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.907886    2966 server_others.go:192] "Using iptables Proxier" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.907956    2966 server_others.go:199] "kube-proxy running in dual-stack mode" ipFamily=IPv4 Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.907988    2966 server_others.go:200] "Creating dualStackProxier for iptables" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.908035    2966 server_others.go:484] "Detect-local-mode set to ClusterCIDR, but no IPv6 cluster CIDR defined, defaulting to no-op detect-local for IPv6" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.908110    2966 proxier.go:253] "Setting route_localnet=1 to allow node-ports on localhost; to change this either disable iptables.localhostNodePorts (--iptables-localhost-nodeports) or set nodePortAddresses (--nodeport-addresses) to filter loopback addresses" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.909672    2966 server.go:658] "Version info" version="v1.27.10+k3s2" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.909725    2966 server.go:660] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK="" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.911794    2966 config.go:188] "Starting service config controller" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.911844    2966 shared_informer.go:311] Waiting for caches to sync for service config Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.911886    2966 config.go:97] "Starting endpoint slice config controller" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.911899    2966 shared_informer.go:311] Waiting for caches to sync for endpoint slice config Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.912955    2966 config.go:315] "Starting node config controller" Aug  1 19:23:15 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:15.912997    2966 shared_informer.go:311] Waiting for caches to sync for node config Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:16.011969    2966 shared_informer.go:318] Caches are synced for endpoint slice config Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:16.012000    2966 shared_informer.go:318] Caches are synced for service config Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:16.013121    2966 shared_informer.go:318] Caches are synced for node config Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:23:16Z" level=info msg="Tunnel authorizer set Kubelet Port 10250" Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:16.593645    2966 kube.go:152] Node controller sync successful Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:16.594404    2966 vxlan.go:141] VXLAN config: VNI=1 Port=0 GBP=false Learning=false DirectRouting=false Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:16.601768    2966 apiserver.go:52] "Watching apiserver" Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:16.618410    2966 desired_state_of_world_populator.go:153] "Finished populating initial desired state of world" Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:16.622515    2966 reconciler.go:41] "Reconciler: start to sync state" Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:23:16Z" level=info msg="Wrote flannel subnet file to /run/flannel/subnet.env" Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:23:16Z" level=info msg="Running flannel backend." Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:16.632265    2966 iptables.go:290] generated 3 rules Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:16.632315    2966 vxlan_network.go:65] watching for new subnet leases Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:16.634285    2966 subnet.go:159] Batch elem [0] is { lease.Event{Type:0, Lease:lease.Lease{EnableIPv4:true, EnableIPv6:false, Subnet:ip.IP4Net{IP:0xaf40000, PrefixLen:0x18}, IPv6Subnet:ip.IP6Net{IP:(*ip.IP6)(nil), PrefixLen:0x0}, Attrs:lease.LeaseAttrs{PublicIP:0xa000002, PublicIPv6:(*ip.IP6)(nil), BackendType:"vxlan", BackendData:json.RawMessage{0x7b, 0x22, 0x56, 0x4e, 0x49, 0x22, 0x3a, 0x31, 0x2c, 0x22, 0x56, 0x74, 0x65, 0x70, 0x4d, 0x41, 0x43, 0x22, 0x3a, 0x22, 0x37, 0x65, 0x3a, 0x66, 0x37, 0x3a, 0x37, 0x63, 0x3a, 0x62, 0x36, 0x3a, 0x30, 0x30, 0x3a, 0x62, 0x37, 0x22, 0x7d}, BackendV6Data:json.RawMessage(nil)}, Expiration:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), Asof:0}} } Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:16.636521    2966 iptables.go:290] generated 7 rules Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:16.665070    2966 iptables.go:283] bootstrap done Aug  1 19:23:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:23:16.693711    2966 iptables.go:283] bootstrap done Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[1]: Created slice User Slice of UID 0. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[1]: Starting User Runtime Directory /run/user/0... Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[1]: Finished User Runtime Directory /run/user/0. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[1]: Starting User Manager for UID 0... Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Queued start job for default target Main User Target. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Created slice User Application Slice. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Reached target Paths. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Reached target Timers. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Starting D-Bus User Message Bus Socket... Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Listening on GnuPG network certificate management daemon. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Listening on GnuPG cryptographic agent and passphrase cache. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Listening on debconf communication socket. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Listening on REST API socket for snapd user session agent. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Listening on D-Bus User Message Bus Socket. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Reached target Sockets. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Reached target Basic System. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[1]: Started User Manager for UID 0. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[1]: Started Session 13 of User root. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Reached target Main User Target. Aug  1 19:23:37 test-cx22-pool-small-static-worker1 systemd[3139]: Startup finished in 151ms. Aug  1 19:23:54 test-cx22-pool-small-static-worker1 systemd[1]: session-13.scope: Deactivated successfully. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[1]: Stopping User Manager for UID 0... Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Stopped target Main User Target. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Stopped target Basic System. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Stopped target Paths. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Stopped target Sockets. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Stopped target Timers. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Closed D-Bus User Message Bus Socket. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Closed GnuPG network certificate management daemon. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Closed GnuPG cryptographic agent and passphrase cache (restricted). Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Closed GnuPG cryptographic agent (ssh-agent emulation). Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Closed GnuPG cryptographic agent and passphrase cache. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Closed debconf communication socket. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Closed REST API socket for snapd user session agent. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Removed slice User Application Slice. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Reached target Shutdown. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Finished Exit the Session. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[3139]: Reached target Exit the Session. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[1]<EMAIL_ADDRESS>Deactivated successfully. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[1]: Stopped User Manager for UID 0. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[1]: Stopping User Runtime Directory /run/user/0... Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[1]: run-user-0.mount: Deactivated successfully. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[1]<EMAIL_ADDRESS>Deactivated successfully. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[1]: Stopped User Runtime Directory /run/user/0. Aug  1 19:24:04 test-cx22-pool-small-static-worker1 systemd[1]: Removed slice User Slice of UID 0. Aug  1 19:24:06 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:24:06Z" level=error msg="Remotedialer proxy error" error="websocket: close 1006 (abnormal closure): unexpected EOF" Aug  1 19:24:11 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:24:11Z" level=info msg="Connecting to proxy" url="wss://<IP_ADDRESS>:6443/v1-k3s/connect" Aug  1 19:24:11 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:24:11Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp <IP_ADDRESS>:6443: connect: connection refused" Aug  1 19:24:11 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:24:11Z" level=error msg="Remotedialer proxy error" error="dial tcp <IP_ADDRESS>:6443: connect: connection refused" Aug  1 19:24:16 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:24:16Z" level=info msg="Connecting to proxy" url="wss://<IP_ADDRESS>:6443/v1-k3s/connect" Aug  1 19:24:16 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:24:16Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp <IP_ADDRESS>:6443: connect: connection refused" Aug  1 19:24:16 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:24:16Z" level=error msg="Remotedialer proxy error" error="dial tcp <IP_ADDRESS>:6443: connect: connection refused" Aug  1 19:24:16 test-cx22-pool-small-static-worker1 k3s[2966]: E0801 19:24:16.818376    2966 controller.go:193] "Failed to update lease" err="Put \"https://<IP_ADDRESS>:6444/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/test-cx22-pool-small-static-worker1?timeout=10s\": read tcp <IP_ADDRESS>:57348-><IP_ADDRESS>:6444: read: connection reset by peer" Aug  1 19:24:16 test-cx22-pool-small-static-worker1 k3s[2966]: E0801 19:24:16.819609    2966 controller.go:193] "Failed to update lease" err="Put \"https://<IP_ADDRESS>:6444/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/test-cx22-pool-small-static-worker1?timeout=10s\": read tcp <IP_ADDRESS>:57358-><IP_ADDRESS>:6444: read: connection reset by peer" Aug  1 19:24:16 test-cx22-pool-small-static-worker1 k3s[2966]: E0801 19:24:16.820828    2966 controller.go:193] "Failed to update lease" err="Put \"https://<IP_ADDRESS>:6444/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/test-cx22-pool-small-static-worker1?timeout=10s\": read tcp <IP_ADDRESS>:57368-><IP_ADDRESS>:6444: read: connection reset by peer" Aug  1 19:24:16 test-cx22-pool-small-static-worker1 k3s[2966]: E0801 19:24:16.822305    2966 controller.go:193] "Failed to update lease" err="Put \"https://<IP_ADDRESS>:6444/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/test-cx22-pool-small-static-worker1?timeout=10s\": read tcp <IP_ADDRESS>:57382-><IP_ADDRESS>:6444: read: connection reset by peer" Aug  1 19:24:16 test-cx22-pool-small-static-worker1 k3s[2966]: E0801 19:24:16.823959    2966 controller.go:193] "Failed to update lease" err="Put \"https://<IP_ADDRESS>:6444/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/test-cx22-pool-small-static-worker1?timeout=10s\": read tcp <IP_ADDRESS>:57394-><IP_ADDRESS>:6444: read: connection reset by peer" Aug  1 19:24:16 test-cx22-pool-small-static-worker1 k3s[2966]: I0801 19:24:16.824037    2966 controller.go:116] "failed to update lease using latest lease, fallback to ensure lease" err="failed 5 attempts to update lease" Aug  1 19:24:17 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:24:17Z" level=error msg="Error getting the node object: Get \"https://<IP_ADDRESS>:6444/api/v1/nodes/test-cx22-pool-small-static-worker1\": read tcp <IP_ADDRESS>:57588-><IP_ADDRESS>:6444: read: connection reset by peer - error from a previous attempt: read tcp <IP_ADDRESS>:57344-><IP_ADDRESS>:6444: read: connection reset by peer" Aug  1 19:24:17 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:24:17Z" level=fatal msg="Get \"https://<IP_ADDRESS>:6444/api/v1/nodes/test-cx22-pool-small-static-worker1\": read tcp <IP_ADDRESS>:57588-><IP_ADDRESS>:6444: read: connection reset by peer - error from a previous attempt: read tcp <IP_ADDRESS>:57344-><IP_ADDRESS>:6444: read: connection reset by peer" Aug  1 19:24:17 test-cx22-pool-small-static-worker1 systemd[1]: k3s-agent.service: Main process exited, code=exited, status=1/FAILURE Aug  1 19:24:17 test-cx22-pool-small-static-worker1 systemd[1]: k3s-agent.service: Failed with result 'exit-code'. Aug  1 19:24:17 test-cx22-pool-small-static-worker1 systemd[1]: Failed to start Lightweight Kubernetes. Aug  1 19:24:17 test-cx22-pool-small-static-worker1 systemd[1]: k3s-agent.service: Consumed 3.319s CPU time. Aug  1 19:24:22 test-cx22-pool-small-static-worker1 systemd[1]: k3s-agent.service: Scheduled restart job, restart counter is at 4. Aug  1 19:24:22 test-cx22-pool-small-static-worker1 systemd[1]: Stopped Lightweight Kubernetes. Aug  1 19:24:22 test-cx22-pool-small-static-worker1 systemd[1]: k3s-agent.service: Consumed 3.319s CPU time. Aug  1 19:24:22 test-cx22-pool-small-static-worker1 systemd[1]: Starting Lightweight Kubernetes... Aug  1 19:24:22 test-cx22-pool-small-static-worker1 sh[3240]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service Aug  1 19:24:23 test-cx22-pool-small-static-worker1 k3s[3244]: time="2024-08-01T19:24:23Z" level=info msg="Starting k3s agent v1.27.10+k3s2 (5b2ac881)" Aug  1 19:24:23 test-cx22-pool-small-static-worker1 k3s[3244]: time="2024-08-01T19:24:23Z" level=info msg="Adding server to load balancer k3s-agent-load-balancer: <IP_ADDRESS>:6443" Aug  1 19:24:23 test-cx22-pool-small-static-worker1 k3s[3244]: time="2024-08-01T19:24:23Z" level=info msg="Running load balancer k3s-agent-load-balancer <IP_ADDRESS>:6444 -> [<IP_ADDRESS>:6443] [default: <IP_ADDRESS>:6443]" Aug  1 19:24:23 test-cx22-pool-small-static-worker1 k3s[3244]: time="2024-08-01T19:24:23Z" level=warning msg="Cluster CA certificate is not trusted by the host CA bundle, but the token does not include a CA hash. Use the full token from the server's node-token file to enable Cluster CA validation." Aug  1 19:24:23 test-cx22-pool-small-static-worker1 k3s[3244]: time="2024-08-01T19:24:23Z" level=info msg="Waiting to retrieve agent configuration; server is not ready: https://<IP_ADDRESS>:6444/v1-k3s/serving-kubelet.crt: 503 Service Unavailable" Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[1]: Created slice User Slice of UID 0. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[1]: Starting User Runtime Directory /run/user/0... Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[1]: Finished User Runtime Directory /run/user/0. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[1]: Starting User Manager for UID 0... Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Queued start job for default target Main User Target. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Created slice User Application Slice. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Reached target Paths. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Reached target Timers. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Starting D-Bus User Message Bus Socket... Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Listening on GnuPG network certificate management daemon. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Listening on GnuPG cryptographic agent and passphrase cache. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Listening on debconf communication socket. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Listening on REST API socket for snapd user session agent. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Listening on D-Bus User Message Bus Socket. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Reached target Sockets. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Reached target Basic System. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Reached target Main User Target. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[3258]: Startup finished in 189ms. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[1]: Started User Manager for UID 0. Aug  1 19:24:26 test-cx22-pool-small-static-worker1 systemd[1]: Started Session 15 of User root.
Latest available version v1.30.3+k3s1:

Local (deployment) machine log output:

`hetzner-k3s create --config vito_botta_test_cluster_config.yaml
Validating configuration......configuration seems valid.
=== Creating infrastructure resources ===
Creating network...done.
Creating firewall...done.
Creating SSH key...done.
Creating placement group test-masters...done.
Creating placement group test-small-static-1...done.
Creating server test-cx22-master1...
Creating server test-cx22-pool-small-static-worker1...
...server test-cx22-master1 created.
...server test-cx22-pool-small-static-worker1 created.
Server test-cx22-master1 already exists, skipping.
Waiting for successful ssh connectivity with server test-cx22-master1...
Server test-cx22-pool-small-static-worker1 already exists, skipping.
Waiting for successful ssh connectivity with server test-cx22-pool-small-static-worker1...
...server test-cx22-master1 is now up.
...server test-cx22-pool-small-static-worker1 is now up.
=== Setting up Kubernetes ===
Deploying k3s to first master test-cx22-master1...
[INFO]  Using v1.30.3+k3s1 as release
[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.30.3+k3s1/sha256sum-amd64.txt
[INFO]  Downloading binary https://github.com/k3s-io/k3s/releases/download/v1.30.3+k3s1/k3s
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
[INFO]  Skipping installation of SELinux RPM
[INFO]  Creating /usr/local/bin/kubectl symlink to k3s
[INFO]  Creating /usr/local/bin/crictl symlink to k3s
[INFO]  Creating /usr/local/bin/ctr symlink to k3s
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s.service
[INFO]  systemd: Enabling k3s unit
[INFO]  systemd: Starting k3s
Waiting for the control plane to be ready...
Saving the kubeconfig file to ~/test/kubeconfig...
...k3s has been deployed to first master test-cx22-master1 and the control plane is up.
Deploying k3s to worker test-cx22-pool-small-static-worker1...
[INFO]  Using v1.30.3+k3s1 as release
[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.30.3+k3s1/sha256sum-amd64.txt
[INFO]  Downloading binary https://github.com/k3s-io/k3s/releases/download/v1.30.3+k3s1/k3s
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
[INFO]  Skipping installation of SELinux RPM
[INFO]  Creating /usr/local/bin/kubectl symlink to k3s
[INFO]  Creating /usr/local/bin/crictl symlink to k3s
[INFO]  Creating /usr/local/bin/ctr symlink to k3s
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-agent-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s-agent.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s-agent.service
[INFO]  systemd: Enabling k3s-agent unit
[INFO]  systemd: Starting k3s-agent`

Syslog from worker node (k3s-agent):
Aug  1 20:04:23 test-cx22-pool-small-static-worker1 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Aug  1 20:04:24 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:24Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:26 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:26Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:28 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:28Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:30 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:30Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:32 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:32Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:34 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:34Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:36 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:36Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:38 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:38Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:40 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:40Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:42 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:42Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:44 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:44Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:46 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:46Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:48 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:48Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:50 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:50Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:52 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:52Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:54 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:54Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:56 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:56Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:04:58 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:04:58Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:00 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:00Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:02 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:02Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:04 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:04Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:06 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:06Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:08 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:08Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:10 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:10Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:12 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:12Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:14 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:14Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:16 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:16Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:18 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:18Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:20 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:20Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:22 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:22Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:24 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:24Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:26 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:26Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:28 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:28Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:30 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:30Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:32 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:32Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:34 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:34Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:36 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:36Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:38 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:38Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:40 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:40Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:42 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:42Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:44 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:44Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:46 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:46Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:48 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:48Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:50 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:50Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:52 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:52Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:54 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:54Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:56 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:56Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:05:58 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:05:58Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:00 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:00Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:02 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:02Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:04 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:04Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:06 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:06Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:08 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:08Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:10 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:10Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:12 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:12Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:14 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:14Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:16 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:16Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:18 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:18Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:20 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:20Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:22 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:22Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:24 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:24Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:26 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:26Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:28 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:28Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:30 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:30Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:32 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:32Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:34 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:34Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:36 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:36Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:38 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:38Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:40 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:40Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:42 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:42Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:44 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:44Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:46 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:46Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:48 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:48Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:50 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:50Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:52 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:52Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:54 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:54Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:56 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:56Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:06:58 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:06:58Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:00 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:00Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:02 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:02Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:04 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:04Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:06 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:06Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:08 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:08Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:10 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:10Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:12 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:12Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:14 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:14Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:16 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:16Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:18 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:18Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:20 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:20Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:22 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:22Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:24 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:24Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:26 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:26Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:28 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:28Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:30 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:30Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:32 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:32Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:34 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:34Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:36 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:36Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:38 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:38Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:40 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:40Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:42 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:42Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:44 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:44Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:46 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:46Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:48 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:48Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:50 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:50Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:52 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:52Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:54 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:54Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:56 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:56Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:07:58 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:07:58Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:00 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:00Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:02 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:02Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:04 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:04Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:06 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:06Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:08 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:08Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:10 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:10Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:11 test-cx22-pool-small-static-worker1 systemd[1]: session-13.scope: Deactivated successfully. Aug  1 20:08:12 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:12Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:14 test-cx22-pool-small-static-worker1 systemd[1]: Starting Download data for packages that failed at package install time... Aug  1 20:08:14 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:14Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:14 test-cx22-pool-small-static-worker1 systemd[1]: update-notifier-download.service: Deactivated successfully. Aug  1 20:08:14 test-cx22-pool-small-static-worker1 systemd[1]: Finished Download data for packages that failed at package install time. Aug  1 20:08:16 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:16Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:18 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:18Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:20 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:20Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:22 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:22Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:24 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:24Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:26 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:26Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:28 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:28Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:30 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:30Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:32 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:32Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:34 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:34Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:36 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:36Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:38 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:38Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:40 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:40Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:42 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:42Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:44 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:44Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:46 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:46Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:48 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:48Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:50 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:50Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:52 test-cx22-pool-small-static-worker1 k3s[2304]: time="2024-08-01T20:08:52Z" level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint" Aug  1 20:08:52 test-cx22-pool-small-static-worker1 systemd[1]: Started Session 14 of User root.

Hi, can you post

./hetzner-k3s --version
your config.yaml

To me the first run failure looks like a firewall problem - could you reach <IP_ADDRESS> on port 6443?
At the second run the problem is not clear - did it time out?
PS: No Stress but would be nice to get those long logs formatted, so that a line start is at a line start, plus put into a <details><summary>syslog</summary>..... </details> section :-)

Thanks for such a fast reply! @axgkl
Just an important note to mention, everything above the version of k3s v1.27.9+k3s1 seems not working.
hetzner-k3s version: 1.1.5
config:
`---
hetzner_token: xyz
cluster_name: test
kubeconfig_path: "./kubeconfig"
#k3s_version: v1.26.4+k3s1 # worked
#k3s_version: v1.27.15+k3s2 # not working
#k3s_version: v1.27.2-rc2+k3s1 # working
#k3s_version: v1.27.8+k3s2 # working
#k3s_version: v1.27.10+k3s2 # not working agent does not start
#k3s_version: v1.27.10-rc1+k3s2 # not working
#k3s_version: v1.27.9+k3s1 # last working
#k3s_version: v1.27.10-rc1+k3s1 # not working
k3s_version: v1.30.3+k3s1 # not working
public_ssh_key_path: "~/.ssh/id_rsa.pub"
private_ssh_key_path: "~/.ssh/id_rsa"
use_ssh_agent: false # set to true if your key has a passphrase or if SSH connections don't work or seem to hang without agent. See https://github.com/vitobotta/hetzner-k3s#limitations
ssh_port: 22
ssh_allowed_networks:

<IP_ADDRESS>/0 # ensure your current IP is included in the range
api_allowed_networks:
<IP_ADDRESS>/0 # ensure your current IP is included in the range
private_network_subnet: <IP_ADDRESS>/16 # ensure this doesn't overlap with other networks in the same project
disable_flannel: false # set to true if you want to install a different CNI
schedule_workloads_on_masters: false

cluster_cidr: <IP_ADDRESS>/16 # optional: a custom IPv4/IPv6 network CIDR to use for pod IPs
service_cidr: <IP_ADDRESS>/16 # optional: a custom IPv4/IPv6 network CIDR to use for service IPs. Warning, if you change this, you should also change cluster_dns!
cluster_dns: <IP_ADDRESS> # optional: IPv4 Cluster IP for coredns service. Needs to be an address from the service_cidr range
enable_public_net_ipv4: false # default is true
enable_public_net_ipv6: false # default is true
image: rocky-9 # optional: default is ubuntu-22.04
autoscaling_image: 103908130 # optional, defaults to the image setting
snapshot_os: microos # optional: specified the os type when using a custom snapshot
cloud_controller_manager_manifest_url: "https://github.com/hetznercloud/hcloud-cloud-controller-manager/releases/download/v1.19.0/ccm-networks.yaml"
csi_driver_manifest_url: "https://raw.githubusercontent.com/hetznercloud/csi-driver/v2.6.0/deploy/kubernetes/hcloud-csi.yml"
system_upgrade_controller_deployment_manifest_url: "https://github.com/rancher/system-upgrade-controller/releases/download/v0.13.4/system-upgrade-controller.yaml"
system_upgrade_controller_crd_manifest_url: "https://github.com/rancher/system-upgrade-controller/releases/download/v0.13.4/crd.yaml"
cluster_autoscaler_manifest_url: "https://raw.githubusercontent.com/kubernetes/autoscaler/master/cluster-autoscaler/cloudprovider/hetzner/examples/cluster-autoscaler-run-on-master.yaml"
datastore:
mode: etcd # etcd (default) or external
external_datastore_endpoint: postgres://....
masters_pool:
instance_type: cx22
instance_count: 1
location: nbg1
worker_node_pools:

name: small-static
instance_type: cx22
instance_count: 1
location: nbg1
image: debian-11
labels:
- key: purpose
value: blah
taints:
- key: something
value: value1:NoSchedule

name: big-autoscaled
instance_type: cx22
instance_count: 1
location: nbg1
autoscaling:
enabled: true
min_instances: 0
max_instances: 3

additional_packages:
- somepackage
post_create_commands:
- apt update
- apt upgrade -y
- apt autoremove -y
enable_encryption: true
existing_network: <specify if you want to use an existing network, otherwise one will be created for this cluster>
kube_api_server_args:
- arg1
- ...
kube_scheduler_args:
- arg1
- ...
kube_controller_manager_args:
- arg1
- ...
kube_cloud_controller_manager_args:
- arg1
- ...
kubelet_args:
- arg1
- ...
kube_proxy_args:
- arg1
- ...
api_server_hostname: k8s.example.com # optional: DNS for the k8s API LoadBalancer. After the script has run, create a DNS record with the address of the API LoadBalancer.`

@axgkl
Here are all the logs in readable form:[hetzner_k3s_bug_resolving(https://github.com/jankohout95/hetzner_k3s_bug_resolving)
Btw,
Error 1:
curl --insecure https://<IP_ADDRESS>:6443 {   "kind": "Status",   "apiVersion": "v1",   "metadata": {},   "status": "Failure",   "message": "Unauthorized",   "reason": "Unauthorized",   "code": 401 }
Error 2: I left it running for a couple of minutes with no timeout, so it seems like there is no default value for this type of connection.

Hi, looking at your error 1 syslog, this here puzzles me:
Failed connects to master
```
  ~❯ cat syslog| grep 'ailed to connect to proxy'
Aug  1 19:20:03 test-cx22-pool-small-static-worker1 k3s[2319]: time="2024-08-01T19:20:03Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp <IP_ADDRESS>:6443: connect: connection refused"
Aug  1 19:20:08 test-cx22-pool-small-static-worker1 k3s[2319]: time="2024-08-01T19:20:08Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp <IP_ADDRESS>:6443: connect: connection refused"
Aug  1 19:21:26 test-cx22-pool-small-static-worker1 k3s[2572]: time="2024-08-01T19:21:26Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp <IP_ADDRESS>:6443: connect: connection refused"
Aug  1 19:21:31 test-cx22-pool-small-static-worker1 k3s[2572]: time="2024-08-01T19:21:31Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp <IP_ADDRESS>:6443: connect: connection refused"
Aug  1 19:22:46 test-cx22-pool-small-static-worker1 k3s[2768]: time="2024-08-01T19:22:46Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp <IP_ADDRESS>:6443: connect: connection refused"
Aug  1 19:22:51 test-cx22-pool-small-static-worker1 k3s[2768]: time="2024-08-01T19:22:51Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp <IP_ADDRESS>:6443: connect: connection refused"
Aug  1 19:24:11 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:24:11Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp <IP_ADDRESS>:6443: connect: connection refused"
Aug  1 19:24:16 test-cx22-pool-small-static-worker1 k3s[2966]: time="2024-08-01T19:24:16Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp <IP_ADDRESS>:6443: connect: connection refused"
```

Hi could never successfully connect to the master via the internal network - over 4 Minutes, leading to an exit and attempted restart of the k3s-agent.
I got a hetzner status error yesterday about issues with their private ip networks, maybe it's that?
To crosscheck: Can you attempt now to connect to <IP_ADDRESS> port 6443, from the worker at <IP_ADDRESS>? Is that port reachable now?
And IF that port is reachable:
Whats the status of systemctl status k3s-agent on your worker now?
Also try restarting it and look at the journal.
Regarding version differences I can say nothing, not an expert on different k3s versions. I personally tend to think those connect issues are independent of those versions.

Hi @axgkl,
I was trying the same process multiple times with v1.27.9+k3s1 and it was working without any issues. E.g., creating and deleting clusters 5 times in a row. That was working with this particular version, so I am pretty sure it is version-related.
The status of the agent was "enabled", but it has not started. I did not try to restart it, because I hoped it would self-heal.

Hi @axgkl,
still the same scenario, I doubt the problem with Hetzner networking.

I also cannot set up new clusters with newer k8s versions. Upgrading old clusters to 1.30 works but not setting up new ones. k8s 1.28.5 still works but 1.28.11 is already broken.
I'm gathering more info about what might be wrong and will report back.

Adding new nodes directly with 1.30+ also works, so I assume that something in the setup process of the master that starts to break in later versions.
My config is quite straight-forward:
cluster_name: test
kubeconfig_path: "./kubeconfig"
k3s_version: v1.30.2+k3s2
public_ssh_key_path: "~/.ssh/id_rsa.pub"
private_ssh_key_path: "~/.ssh/id_rsa"
use_ssh_agent: true
ssh_allowed_networks:
  - <IP_ADDRESS>/0
api_allowed_networks:
  - <IP_ADDRESS>/0
schedule_workloads_on_masters: false
masters_pool:
  instance_type: cax11
  instance_count: 1
  location: fsn1
worker_node_pools:
  - name: x86
    image: ubuntu-24.04
    instance_type: cax11
    instance_count: 1
    location: fsn1
additional_packages:
  - nfs-common
kubelet_args:
  - "eviction-hard=memory.available\\<200Mi"

I wonder if the problem is network related, the master logs show this:
level=warning msg="no subnet found for key: FLANNEL_NETWORK in file: /run/flannel/subnet.env"
level=warning msg="no subnet found for key: FLANNEL_SUBNET in file: /run/flannel/subnet.env"
level=warning msg="no subnet found for key: FLANNEL_IPV6_NETWORK in file: /run/flannel/subnet.env"
level=warning msg="no subnet found for key: FLANNEL_IPV6_SUBNET in file: /run/flannel/subnet.env"

and later an error like this is shown multiple times:
level=info msg="Network policy controller waiting for removal of node.cloudprovider.kubernetes.io/uninitialized taint"

I think it's this change in k3s-1.28.6 (https://docs.k3s.io/release-notes/v1.28.X#changes-since-v1285k3s1):

Wait for taint to be gone in the node before starting the netpol controller (#9175)

Maybe the result is a chicken-egg situation. If I understand correctly the node.cloudprovider.kubernetes.io/uninitialized taint will only be removed when the CCM is running. However, hetzner-k3s is deploying the CCM only after the workers. The worker systemd services however never finish activating completely because of the taint and so hetzner-k3s never gets to install the CCM...
A simple workaround is to set the number of worker to 0 for the initial install and then run again with the final number.

@vitobotta See the @jrudolph's comment above - just to make sure this does not escape your attention, crazy good find, imho. Should we deploy any static workers only after the CCM in general?

I think I addressed this in the WIP v2 already, as the software is installed before provisioning the worker nodes. Can you try and see if you can reproduce the issue using v2?

I think I addressed this in the WIP v2 already, as the software is installed before provisioning the worker nodes. Can you try and see if you can reproduce the issue using v2?

I have only quickly tried v2 (because I try to not change everything at once and I'm already in the process of a largish infrastructure overhaul..), and it failed with some non-descriptive error I didn't want to debug yet, but I can have another try and report in the v2 discussion thread.

I think I addressed this in the WIP v2 already, as the software is installed before provisioning the worker nodes. Can you try and see if you can reproduce the issue using v2?

I have only quickly tried v2 (because I try to not change everything at once and I'm already in the process of a largish infrastructure overhaul..), and it failed with some non-descriptive error I didn't want to debug yet, but I can have another try and report in the v2 discussion thread.

I just replied there. I'd open a separate issue if you are having what seems a problem with the config file when using v2.

I'm closing this, please open a separate issue for v2 if you still have problems with that version, since I will release it soon.


restic tests fails on arm with unexpected error: operation not supported

We are having some issues with restic package in Gentoo, while trying to execute restic-0.11.0 tests on arm the next error occur:

=== RUN   TestPreallocate/1
preallocate_test.go:25: unexpected error: operation not supported

=== RUN   TestPreallocate/4096
preallocate_test.go:25: unexpected error: operation not supported

=== RUN   TestPreallocate/1048576
preallocate_test.go:25: unexpected error: operation not supported

--- FAIL: TestPreallocate (0.01s)
    --- PASS: TestPreallocate/0 (0.00s)
    --- FAIL: TestPreallocate/1 (0.00s)
    --- FAIL: TestPreallocate/4096 (0.00s)
    --- FAIL: TestPreallocate/1048576 (0.00s)

Note that this error seems to happen also with version 0.9.6, and in both cases it happens in arm and arm64.

Which filesystem is used for the tmp directory? The tests currently assume that preallocate works there. However, it would be possible to skip that test if operation not supported is returned. The restorer code uses preallocate as an optional optimization and still works even if the preallocation fails.
That error cannot occur for restic 0.9.6, the preallocate implementation didn't exist back then.

This error was reported by a gentoo dev (not myself), I'm still setting up an arm set-up to test this. Version 0.9.6 had also some tests failures on arm, maybe not the same, I will try it out myself when I had the arm set-up ready and report back.
Thank you, I was unaware that the preallocate feature was fs dependent.

The test works fine on my raspberry pi (using raspbian). Could you try whether #3319 solves the problem for you?

Seems that the environment changed and now the tests passed. I don't why, it's very weird. I will close this issue for now.


Enable access markers at -O when -enforce-exclusivity is explicit.

-enforce-exclusivity=checked now does what it says. It emits checks at -O, not
just -Onone.
This does not change the default.
-Onone default: -enforce-exclusivity=checked
-O default: -enforce-exclusivity=unchecked

@swift-ci test.

@swift-ci smoke test and merge.


Existing releases are no longer updated

I currently use a matrix to generate jobs, each has the same payload just different file when creating a release.
https://github.com/debdutdeb/novm/blob/cf13d8741fee6959d72dd8bae05cdb5750ca30e9/.github/workflows/release.yaml#L20-L44
This used to just update the existing release with the new files (adding one by one as they are built), noticed recently, that isn't the case anymore. I've been getting Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}
Looking at the changes, I think the problem lies in https://github.com/softprops/action-gh-release/pull/386 although don't know exactly what, likely octokit is adding something more to the request causing this to fail. Or more likely doing some pre-flight checks like "does the tag exist?".
Trying the commit right before this one, seems to have helped my workflow to work again.
commit
your commit
workflow result

We're also running into this issue after upgrading to v2.

We have the same issue. Both v1 and v2 do not work anymore.

We are having this problem now, so with each release I have to manually download all the assets from 5 releases, delete them, and upload them all to a 6th, which is quite annoying.
Does anyone have a fix for this?

Yeah same issue, surprised this still has yet to be fixed.

Does anyone know another action which can replace this one? Now that this one no longer works and seems to be unmaintained or slowly maintained.

I found a solution that worked for me. While I’m not entirely sure if it's directly related to this issue, it might be helpful.
The action was functioning well before, but after an update, I encountered the error: "Pattern * does not match any files," similar to the issue in #414. As a result, no files were uploaded.
After extensive searching, I discovered that the paths I had specified in the action were directories instead of files. (I used ls -l for debugging, as in #79)
Now, I use the following step to upload all files from my build folder, and it works perfectly:
      - name: "Upload Release"
        uses: softprops/action-gh-release@v2
        if: startsWith(github.ref, 'refs/tags/')
        with:
          files: |
            build/*

I hope this helps you as well.

I found a solution that worked for me. While I’m not entirely sure if it's directly related to this issue, it might be helpful.
The action was functioning well before, but after an update, I encountered the error: "Pattern * does not match any files," similar to the issue in #414. As a result, no files were uploaded.
After extensive searching, I discovered that the paths I had specified in the action were directories instead of files. (I used ls -l for debugging, as in #79)
Now, I use the following step to upload all files from my build folder, and it works perfectly:
      - name: "Upload Release"
        uses: softprops/action-gh-release@v2
        if: startsWith(github.ref, 'refs/tags/')
        with:
          files: |
            build/*

I hope this helps you as well.

This work for me ,  in matrix is work!

When used in a matrix, uploading files with different names to the same tag will only work properly in a few cases, and most of the time it will report an error.
⚠ Unexpected error fetching GitHub release for tag refs/heads/test: HttpError: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"} - https://docs.github.com/rest/releases/releases#update-a-release
Error: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"} - https://docs.github.com/rest/releases/releases#update-a-release

When used in a matrix, uploading files with different names to the same tag will only work properly in a few cases, and most of the time it will report an error.
⚠ Unexpected error fetching GitHub release for tag refs/heads/test: HttpError: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"} - https://docs.github.com/rest/releases/releases#update-a-release
Error: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"} - https://docs.github.com/rest/releases/releases#update-a-release

Setting the job strategy.max-parallel to 1 prevents this issue, at the expense of longer build times.
It looks like a race condition on the GitHub side if the same release is being created at the same time by different jobs.
The action should wait a little and retry in this specific error.

When used in a matrix, uploading files with different names to the same tag will only work properly in a few cases, and most of the time it will report an error.
⚠ Unexpected error fetching GitHub release for tag refs/heads/test: HttpError: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"} - https://docs.github.com/rest/releases/releases#update-a-release
Error: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"} - https://docs.github.com/rest/releases/releases#update-a-release

Setting the job strategy.max-parallel to 1 prevents this issue, at the expense of longer build times.
It looks like a race condition on the GitHub side if the same release is being created at the same time by different jobs.
The action should wait a little and retry in this specific error.

The purpose of using matrix is to make the job run concurrently. Your solution of strategy.max-parallel to 1 has lost the meaning of matrix, which is not a fundamental solution to the problem.
I currently have more than 40 matrix parallels. If I set parallel to 1, it will be a disaster and the github action will time out. But thank you for your reply.

When used in a matrix, uploading files with different names to the same tag will only work properly in a few cases, and most of the time it will report an error.
⚠ Unexpected error fetching GitHub release for tag refs/heads/test: HttpError: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"} - https://docs.github.com/rest/releases/releases#update-a-release
Error: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"} - https://docs.github.com/rest/releases/releases#update-a-release

Setting the job strategy.max-parallel to 1 prevents this issue, at the expense of longer build times.
It looks like a race condition on the GitHub side if the same release is being created at the same time by different jobs.
The action should wait a little and retry in this specific error.

The purpose of using matrix is to make the job run concurrently. Your solution of strategy.max-parallel to 1 has lost the meaning of matrix, which is not a fundamental solution to the problem. I currently have more than 40 matrix parallels. If I set parallel to 1, it will be a disaster and the github action will time out. But thank you for your reply.
However, I thought, if I upload the matrix compilation result to Artifacts, and then create a new matrix, each matrix downloads the compilation result from Artifacts and uploads it to the release of the same tag, I wonder if this problem can be solved temporarily by setting strategy.max-parallel to 1. Have you tried it?
I will test whether it is feasible smallprogram/OpenWrtAction@e8e7681
Is it possible that before uploading the result of matrix compilation, I can create an empty tag using softprops/action-gh-release, and then perform the upload operation concurrently in the subsequent matrix, will this solve the problem?

Each matrix job is a separate job running in parallel, meaning each job will try to create or modify the related tagged release. It's possible to upload the artifacts and then create the release at once on another independent job, but this can be painful on some workflows.
To change the tag name you'll need to source a different action that can do this.
I also tried ncipollo/release-action@v1 and it produced the same tag_name already_exists error.
I suggest you try to create an empty release beforehand with the same tag and release type in a step allowed to fail, like this:
      - name: Prepare Release
        uses: softprops/action-gh-release@v2
        continue-on-error: true
        with:
          tag_name: mytag
          make_latest: true

      - name: Publish Release
        uses: softprops/action-gh-release@v2
        with:
          tag_name: mytag
          make_latest: true
          files: ....
          body_path: ....

Looks like this worked out in my case. It's not an actual fix, but it will give some headroom to the GitHub API.

Regarding the problem of uploading files to the same tag name using matrix, I found the ultimate solution and shared it with those who need it.
Solution 1
with performance loss
Can avoid "already_exists","field":"tag_name"

Although this method can avoid the problem, it will lose the advantage of matrix parallelism.
Solution 2

This method requires an extra step to create a tag name without files, and then upload the required matrix in parallel to the previously created tag name. This method has better performance and does not lose the advantage of parallel execution of the matrix.
I hope these two solutions can help those in need.
@lpil @lincolnthalles @andrew121410 @manuelkienlein @debdutdeb

You can use  gh release upload relase_name file_path to upload file to a existing relase, for example:

create a release on tag pushed in release_linux_darwin_targets.yml
upload build artifacts of linux and darwin targets in release_linux_darwin_targets.yml
upload build artifacts of windows targets in release_windows_targets.yml
https://github.com/ascpkg/asc/blob/main/.github/workflows/release_linux_darwin_targets.yml
https://github.com/ascpkg/asc/blob/main/.github/workflows/release_windows_targets.yml

Thank you @capric8416 !


loading src server certificate failed

Hi,
Straightforward brand new set up
Windows 10 client using a gateway to a kali mitm
traffic flow is fine to/fro client to the Internet via kali
I get loading src server certificate failed on port 443 (if (SSL_CTX_use_certificate(sslctx, crt) != 1)). Same behavior if using chrome browser or edge browser on the client, also same behavior when request comes from a locally installed app that attempts authentication to a remote server via port 443
I used https://blog.heckel.xyz/2013/08/04/use-sslsplit-to-transparently-sniff-tls-ssl-connections/ for basic configuration. The sslsplit certificate is installed in trusted root certification authorities on Windows client
Please let me know.
Thanks!
ca_crt.txt
iptables_rules.txt
openssl_version.txt
sslsplit_command.txt
sslsplit_debug_output.txt
sslsplit_V.txt
uname_a.txt
ca.key.txt

This may be related with OpenSSL 1.1.1 (see the comments on issue #242). But I couldn't test it, because I guess you have replaced the actual url with company.net in the debug output, am I right? (My DNS server gives me a different IP for company.net, which goes to sedoparking.com anyway.) If so, can you send me the actual url so I can test with LibreSSL at least?

Hi, thank you very much for your reply!
While I cannot disclose the actual name/IP needed by the locally installed app (NDA related), I get the same behavior when using Google https://www.google.com:443 in any locally installed browsers Windows client, in my case I tested chrome and edge.
Thank you again for taking the time to reply!

If google.com causes the same error, then I am almost certain that it is due to OpenSSL 1.1.1. Can you downgrade OpenSSL to, say, 1.1.0 to see if that will fix it? I hope you are able downgrade OpenSSL, if this is urgent for you.

Duplicate of #248


Get Linux/ThreadStackManagerImpl.h functions prototypes to match plat…

…form/ThreadStackManager.h functions prototypes
Problem
The functions prototypes from platform/ThreadStackManager.h and Linux/ThreadStackManagerImpl.h are differents.
Summary of Changes

Changes the prototypes so they match.

fixes #1548


[RFE] Make container runtime socket path configurable

Current situation
As a follow up to https://github.com/kinvolk/inspektor-gadget/pull/434#issuecomment-998840919, as a prerequisite to #450 and to partially address #184, it would be nice if container runtime socket paths could be configurable.
Impact
Simpler configuration in custom scenarios without increased complexity in default installations.
Ideal future situation
One can use custom container runtime socket paths when using IG locally or in the pod.

@flyth has some branch for this. If anyone wants to work on this, please contact him to avoid double work.


BB-31 - [FEATURE REQUEST] Allow different sudoers files

Sudoers role updates /etc/sudoers file for managing sudo permissions for user or group by default. At times, people may want to create/manage a separate sudoers files for some users or groups and put the sudoers files in /etc/sudoers.d directory.  Modifying /etc/sudoers file may not be the best choice.
Context
We can improve sudoers role to include the option to add sudo permissions in a specified file in /etc/sudoers.d.
Feature
Improvement to collections/infrastructure/roles/sudoers/tasks/main.yml:
- name: lineinfile <|> Add sudoers users and groups
  ansible.builtin.lineinfile:
    dest: "{{ item.file_name | default('/etc/sudoers') }}"
    state: present
    create: true
    owner: root
    group: root
    mode: '0600'
    regexp: "^{{ item.name }}"
    line: "{{ item.name }} {{ item.privilege }}"
    validate: 'visudo -cf %s'
  loop: "{{ sudoers }}"
  when: sudoers is defined and sudoers

The sudoers variable example:
sudoers:
  # Set 'manu' user as sudoer with passwordless rights
  - name: manu
    file_name: "/etc/sudoers.d/mau"
    privilege: ALL=(ALL) NOPASSWD:ALL
  # Set 'techs' group users as sudier with passwordless rights
  - name: "%techs"
    file_name: "/etc/sudoers.d/techs"
    privilege: ALL=(ALL) NOPASSWD:ALL
  - name: greenwood
    privilege: ALL=(ALL) NOPASSWD:ALL

## Additional data

The update continues to support adding user/group to /etc/sudoers while provides an option for creating specified sudoers files for certain users and groups.

Dear @sgaosdgr
Thank you for this feature request ! :blush:
Yes, this is understandable, as it eases a lot users management.
I will work on that asap !

Can you check this PR ? https://github.com/bluebanquise/bluebanquise/pull/916

Thank you.
Simon
On Fri, Mar 29, 2024 at 8:05 AM Benoît Leveugle @.***>
wrote:

Dear @sgaosdgr https://github.com/sgaosdgr
I am starting working on this task 😊
—
Reply to this email directly, view it on GitHub
https://github.com/bluebanquise/bluebanquise/issues/900#issuecomment-2027359753,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWEGVANIJHIUPYBISX54HDTY2VYKHAVCNFSM6AAAAABERQQP3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRXGM2TSNZVGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you for the review. Merged.


JWT help

Try to help get JWT to more recent versions of Django and DRF.

The first step in the ladder will be getting JWT working on DRF 3.2.X.

The project already tests on those versions. I must have been running into bugs. Report the issues and fix them.

Look like this works from master. I guess I'm waiting for a release.