In Kubernetes v1.33, the Backoff Limit Per Index feature has reached general availability. This feature allows users to control the number of retries per index in Indexed Jobs. Previously, the spec.backoffLimit field was not flexible enough for workloads where every index is considered independent. The Backoff Limit Per Index feature addresses this limitation by specifying the number of tolerated Pod failures per index. The spec.backoffLimitPerIndex field is used to specify the number of tolerated Pod failures per index. Additionally, users can fine-tune error handling by specifying a cap on the total number of failed indexes and defining a short-circuit to detect a failed index. When the number of tolerated failures is exceeded, the index is marked as failed and listed in the Job's status.failedIndexes field. An example Job spec snippet demonstrates how to combine Backoff Limit Per Index with the Pod Failure Policy feature. The feature was sponsored by the Kubernetes batch working group and the SIG Apps community. Users interested in working on new features can subscribe to the channel and attend regular community meetings.