Set EC2 instance cache max age to 10 mins

[kishorj]

What type of PR is this?

/kind bug

What this PR does / why we need it:

The AWS in-tree controller caches the EC2 instance information indefinitely unless the nodes get scaled up. In case the EC2 instances have multiple security groups attached, this caching strategy leads to inconsistency between the actual EC2 instance configuration in AWS and the controller's view of the EC2 instance information. This PR sets the maximum age of 10 minutes to the EC2 instance cache.

Once the security group requirements are satisfied, controller will be able to fetch the new EC2 information, and get past the following errors without scaling up the nodes -

• Multiple tagged security groups found for instance i-xxxx ...
• Multiple untagged security groups found for instance i-xxx ...

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Testing

• First setup an EC2 instance with at least 2 security groups, none of them contain the cluster tag. As expected, the in-tree controller fails to provision the load balancer. Attach a cluster tagged security group to the EC2 instances, and verify after the cache expiry controller is able to fetch the updated information without having to scale up the k8s worker nodes.
• Update the EC2 instance security groups configuration, and verify the the controller is able to update the correct security group after the cache expiry.

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

NONE

[k8s-ci-robot]

@kishorj: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[M00nF1sh]

/lgtm
/approve

[kishorj]

/retest

[M00nF1sh]

/lgtm

[andrewsykim]

/approve

(confirming this is a bug fix)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andrewsykim, kishorj, M00nF1sh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• staging/src/k8s.io/legacy-cloud-providers/OWNERS [andrewsykim]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kishorj]

/retest