aws / aws/eks-anywhere

Custom timeout for each stage

Open
#6,123 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.1k
Forks
328
Avg merge
1d 4h
Merged PRs (30d)
9

Description

**What would you like to be added**:
Currently EKSA uses default timeout 5 min for each stage. Need to investigate proper(shorter) timeout for each stage, for each provider.

**Why is this needed**:

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by locating EKSA's default five-minute stage timeout and identifying the stages and providers involved. Done means an agreed timeout policy for each stage and provider, with the resulting behavior validated across those paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.