"type": "host-local",
        "subnet": "10.1.0.0/16",
        "gateway": "10.1.0.1"
      },
      "dns": {
        "nameservers": [ "10.1.0.1" ]
      }
    },
    {
      "type": "tuning",
      "sysctl": {
        "net.core.somaxconn": "500"
      }
    }
  ]

          "10.1.0.1"
        ]
      },
      "ipam": {
        "gateway": "10.1.0.1",
        "subnet": "10.1.0.0/16",
        "type": "host-local"
      },
      "type": "bridge"
    },
    {
      "sysctl": {
        "net.core.somaxconn": "500"
      },
      "type": "tuning"
    },
    {
      "kubernetes": {
        "cni_bin_dir": "/path/cni/bin",
        "kubeconfig": "/path/to/kubeconfig"
      },

          "10.1.0.1"
        ]
      },
      "ipam": {
        "gateway": "10.1.0.1",
        "subnet": "10.1.0.0/16",
        "type": "host-local"
      },
      "type": "bridge"
    },
    {
      "sysctl": {
        "net.core.somaxconn": "500"
      },
      "type": "tuning"
    }
  ]

pkg syscall (linux-386), const PTRACE_SINGLESTEP ideal-int
pkg syscall (linux-386), const PTRACE_SYSCALL ideal-int
pkg syscall (linux-386), const PTRACE_SYSEMU ideal-int
pkg syscall (linux-386), const PTRACE_SYSEMU_SINGLESTEP ideal-int
pkg syscall (linux-386), const PTRACE_TRACEME ideal-int
pkg syscall (linux-386), const PathMax ideal-int
pkg syscall (linux-386), const RLIMIT_AS ideal-int

* The Sysctls experimental feature has been promoted to beta (enabled by default via the `Sysctls` feature flag). PodSecurityPolicy and Pod objects now have fields for specifying and controlling sysctls. Alpha sysctl annotations will be ignored by 1.11+ kubelets. All alpha sysctl annotations in existing deployments must be converted to API fields to be effective. ([#6371](https://github.com/kubernetes/kubernetes/pull/63717), [@ingvagabund](https://github.com/ingvagabund))

pkg syscall (netbsd-arm64), const SYSCTL_VERS_0 = 0
pkg syscall (netbsd-arm64), const SYSCTL_VERS_0 ideal-int
pkg syscall (netbsd-arm64), const SYSCTL_VERS_1 = 16777216
pkg syscall (netbsd-arm64), const SYSCTL_VERS_1 ideal-int
pkg syscall (netbsd-arm64), const SYSCTL_VERSION = 16777216
pkg syscall (netbsd-arm64), const SYSCTL_VERSION ideal-int
pkg syscall (netbsd-arm64), const SYSCTL_VERS_MASK = 4278190080

pkg syscall (darwin-arm64), const SYS___SIGWAIT_NOCANCEL = 422
pkg syscall (darwin-arm64), const SYS___SIGWAIT_NOCANCEL ideal-int
pkg syscall (darwin-arm64), const SYS___SYSCTL = 202
pkg syscall (darwin-arm64), const SYS___SYSCTL ideal-int
pkg syscall (darwin-arm64), const S_IEXEC = 64
pkg syscall (darwin-arm64), const S_IEXEC ideal-int
pkg syscall (darwin-arm64), const S_IFMT = 61440

pkg syscall (freebsd-arm64), const SYS___SETUGID = 374
pkg syscall (freebsd-arm64), const SYS___SETUGID ideal-int
pkg syscall (freebsd-arm64), const SYS___SYSCTL = 202
pkg syscall (freebsd-arm64), const SYS___SYSCTL ideal-int
pkg syscall (freebsd-arm64), const SYS__UMTX_OP = 454
pkg syscall (freebsd-arm64), const SYS__UMTX_OP ideal-int
pkg syscall (freebsd-arm64), const SYS_ABORT2 = 463

- Changes behaviour of kube-proxy start; does not attempt to set specific `sysctl` values (which does not work in recent Kernel versions anymore in non-init namespaces), when the current sysctl values are already set higher. ([#103174](https://github.com/kubernetes/kubernetes/pull/103174), [@Napsty](https://github.com/Napsty))

  
  When the feature gate is enabled, kubelet ignores errors that happens during setting the following sysctl values: `vm.overcommit_memory`, `vm.panic_on_oom`, `kernel.panic`, `kernel.panic_on_oops`, `kernel.keys.root_maxkeys`, `kernel.keys.root_maxbytes`. (These sysctl values for the host, not for the containers)
  
  kubelet also ignores an error during opening `/dev/kmsg`.