Cilium daemonset pods wont rollout restart

/kind bug

**1. What `kops` version are you running? The command `kops version`, will display
this information.**
Client version: 1.34.1 (git-v1.34.1)

**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.**
Client Version: v1.34.4
Kustomize Version: v5.7.1
Server Version: v1.34.4

**3. What cloud provider are you using?**
AWS

**4. What commands did you run? What is the simplest way to reproduce this issue?**
kubectl rollout restart ds cilium -n kube-system

**5. What happened after the commands executed?**
Warning: spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the "appArmorProfile" field instead
Warning: spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the "appArmorProfile" field instead
Warning: spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the "appArmorProfile" field instead
Warning: spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the "appArmorProfile" field instead

**6. What did you expect to happen?**
Cilium daemonset pods restarted

**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.**

```yaml
```

**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.**

**9. Anything else do we need to know?**

Reproduce with `kubectl rollout restart ds cilium -n kube-system` in a kOps AWS cluster using the reported Kubernetes versions. Inspect the Cilium DaemonSet and its pod template after the command, then review the rollout status and warning output. Done means the DaemonSet pods restart as expected without the reported behavior remaining.

Written by the indexing model from the issue text.