chore: add timeoutSeconds to startupProbe in frontend deployments#183
Merged
chore: add timeoutSeconds to startupProbe in frontend deployments#183
Conversation
robodev-r2d2
approved these changes
Dec 16, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a configuration update to the frontend deployment templates for both the admin and standard environments. The main change is the addition of a timeout setting for the container's startup command to improve reliability during initialization.
Deployment configuration improvements:
timeoutSeconds: 30to thespecof bothfrontend/admin-deployment.yamlandfrontend/deployment.yamlto ensure the container startup command does not hang indefinitely. [1] [2]