Kops cluster upgrade from 1.27 to 1.29 create new NLB, Targetgroup and AutoscalingGroup in AWS and also updated new information in old targetgroup

[reddy9694]

/kind bug

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

• Client version: 1.29.0 (git-v1.29.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.

• Client Version: v1.29.5
  Server Version: v1.29.5

3. What cloud provider are you using?

• AWS

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

• kops update cluster <clustername> --lifecycle-overrides IAMRole=ExistsAndWarnIfChanges,IAMRolePolicy=ExistsAndWarnIfChanges,IAMInstanceProfileRole=ExistsAndWarnIfChanges,InternetGateway=ExistsAndWarnIfChanges --yes

5. What happened after the commands executed?

• kops updates cluster from version 1.27 to 1.29 and during the upgrade it says the following

 network_load_balancer.go:333] setting securityGroups on an existing NLB created without securityGroups; will force a new NLB
targetgroup.go:147] found target group but revision "" does not match load balancer revision "******"; will create a new target group

not deleting target-group/<targetgroup-arn> because it is marked for deferred-deletion
not deleting autoscaling-elb-attachment because it is marked for deferred-deletion

6. What did you expect to happen?

• Just a normal version upgrade but don't create new stack (NLB, Targetgroup and AutoscalingGroup in AWS) in AWS.
• If the new stack (NLB, Targetgroup and AutoscalingGroup in AWS) is created, it shouldn't attach the new autoscalinggroup in old targetgroup ( targetgroup before the upgrade )
• How to avoid this issue going forward ? and is this expected with 1.29 version upgrade.

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.

spec:
  api:
    loadBalancer:
      class: Network
      type: Internal

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?