init container - iptables-nft-restore failed

[dbones]

Kuma Version

2.9.3

Describe the bug

deploying the demo application (kumahq/kuma-demo)

as kubernetes sets up the pods, the init container on both (redis, and demo-app), does not work, with a failed code

COMMIT
# [iptables] [1/5] /usr/sbin/iptables-nft-restore --noflush /tmp/iptables-rules.4137472968.txt
# [iptables] [1/5] restoring failed: exit status 4: iptables-nft-restore v1.8.7 (nf_tables): , line 9: RULE_APPEND failed (Operation not supported): rule in chain PREROUTING, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT
# [iptables] [1/5] will try again in 2s
# [iptables] [2/5] /usr/sbin/iptables-nft-restore --noflush /tmp/iptables-rules.4137472968.txt
# [iptables] [2/5] will try again in 2s
# [iptables] [2/5] restoring failed: exit status 4: iptables-nft-restore v1.8.7 (nf_tables): , line 9: RULE_APPEND failed (Operation not supported): rule in chain PREROUTING, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT
# [iptables] [3/5] /usr/sbin/iptables-nft-restore --noflush /tmp/iptables-rules.4137472968.txt
# [iptables] [3/5] restoring failed: exit status 4: iptables-nft-restore v1.8.7 (nf_tables): , line 9: RULE_APPEND failed (Operation not supported): rule in chain PREROUTING, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT
# [iptables] [3/5] will try again in 2s
# [iptables] [4/5] /usr/sbin/iptables-nft-restore --noflush /tmp/iptables-rules.4137472968.txt
# [iptables] [4/5] restoring failed: exit status 4: iptables-nft-restore v1.8.7 (nf_tables): , line 9: RULE_APPEND failed (Operation not supported): rule in chain PREROUTING, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT
# [iptables] [4/5] will try again in 2s
# [iptables] [5/5] /usr/sbin/iptables-nft-restore --noflush /tmp/iptables-rules.4137472968.txt
# [iptables] [5/5] restoring failed: exit status 4: iptables-nft-restore v1.8.7 (nf_tables): , line 9: RULE_APPEND failed (Operation not supported): rule in chain PREROUTING, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT, line 9: RULE_APPEND failed (Operation not supported): rule in chain OUTPUT
Error: failed to setup transparent proxy: unable to restore iptables rules: /usr/sbin/iptables-nft-restore failed

To Reproduce

kuma 2.9.3 has been installed onto the K3s Cluster (Arm CPU) using GitOps

helm chart setttings:

  defaultNamespace: kuma-system
  helm:
    chart: kuma
    repo: https://kumahq.github.io/charts
    version: 2.9.3
    values:
      controlPlane:
        mode: zone
      egress:
        enabled: false

deploy application

kubectl apply -f https://bit.ly/3Kh2Try

Expected behavior

application should be deployed, added to the mesh with a working side car

Additional context (optional)

Cluster

Overview

Pod