/kind bug

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

Tested with these two version
Client version: 1.30.1 (git-v1.30.1)
Client version: 1.30.4 (git-v1.30.4)

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.

1.30.4
1.30.12

3. What cloud provider are you using?

4. What commands did you run? What is the simplest way to reproduce this issue?

With kops edit cluster enabled the imageMaximumGCAge setting in kubelet

spec:
  kubelet:
    imageMaximumGCAge: 24h

kops update cluster
kops rolling-update cluster

5. What happened after the commands executed?

The new node don't came up, and in the syslog I got this error:

Jun 27 09:01:00 *** kubelet[7445]: E0627 09:01:00.750235    7445 run.go:74] "command failed" err="failed to parse kubelet flag: unknown flag: --image-maximum-gc-age"

According to this page, that's an invalid flag:
https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/

6. What did you expect to happen?

Node came up with the imageMaximumGCAge enabled.

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.

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?