You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The hardcoded 40 minutes timeout for the update process is not sufficient, as with machine image being updated, the update can take considerably more to process.
Introduce configuration for this timeout value in the KEB code and helm chart, with default having 120m (2 hours).
SRE would like to specify overrides for this configuration per each KCP environment.
Expected result
KEB update operations have configurable timeout.
Actual result
KEB update operations often ends with failed due to 40 minutes timeout.
Steps to reproduce
Troubleshooting
The text was updated successfully, but these errors were encountered:
Description
The hardcoded 40 minutes timeout for the update process is not sufficient, as with machine image being updated, the update can take considerably more to process.
Introduce configuration for this timeout value in the KEB code and helm chart, with default having 120m (2 hours).
SRE would like to specify overrides for this configuration per each KCP environment.
Expected result
KEB update operations have configurable timeout.
Actual result
KEB update operations often ends with failed due to 40 minutes timeout.
Steps to reproduce
Troubleshooting
The text was updated successfully, but these errors were encountered: