AWS: update the timeout EKS update for the kOps build cluster.

[ameukam]

No description provided.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ameukam

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:

• infra/aws/OWNERS [ameukam]

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

[ameukam]

@bryantbiggs There is no change in the terraform plan. I wonder if the module ignore this change. 🤔

[bryantbiggs]

no - we don't have any ignore on the timeouts, those should always be respected

[ameukam]

I can't see why this is ignored. I can see in the debug logs the ref of the variables:

1009   2024-08-21T19:55:43.871+0200 [DEBUG] ReferenceTransformer: "module.eks.var.cluster_name (expand)" references: [local.cluster_name (expand)]
1010   2024-08-21T19:55:43.871+0200 [DEBUG] ReferenceTransformer: "module.eks.var.cluster_timeouts (expand)" references: []

but no changes:

module.eks.aws_security_group_rule.node["ingress_cluster_8443_webhook"]: Refreshing state... [id=sgrule-2721142640]
module.eks.aws_security_group_rule.cluster["ingress_nodes_443"]: Refreshing state... [id=sgrule-4148544704]
module.eks.aws_eks_cluster.this[0]: Refreshing state... [id=k8s-infra-kops-prow-build]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.

Not sure how to debug this.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale