/kind bug

1. What kops version are you running? The command kops version, will display
this information.

$ kops version
Client version: 1.31.0 (git-v1.31.0)

2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.

$ kubectl version
Client Version: v1.31.3
Kustomize Version: v5.4.2
Server Version: v1.31.5

3. What cloud provider are you using?
AWS

4. What commands did you run? What is the simplest way to reproduce this issue?
No commands, but I cannot find any way to set the cni-exclusive configuration for cilium in the kops cluster spec. I have looked at the Kops documentation and the cilium networking cluster spec docs.

5. What happened after the commands executed?
Just to try and experiment, when I set networking.cilium.cniExclusive: true or networking.cilium.exclusive: true, kops says these are unrecognized, of course because these don't exist

6. What did you expect to happen?
There should be a way to allow setting the cni-exclusive bool. It is hindering us in adopting istio ambinet deployment

7. Please provide your cluster manifest. Execute
kops get --name my.example.com -o yaml to display your cluster manifest.
You may want to remove your cluster name and other sensitive information.
This is the current networking settings in my cluster spec:

  networking:
    cilium:
      bpfLBSockHostNSOnly: true
      etcdManaged: true
      hubble:
        enabled: true

8. Please run the commands with most verbose logging by adding the -v 10 flag.
Paste the logs into this report, or in a gist and provide the gist link here.
NA

9. Anything else do we need to know?
NA