Fix portal rollout timeout by increasing to 600s and adding startup probe#529
Merged
aurelianware merged 1 commit intomainfrom Mar 20, 2026
Merged
Conversation
…robe The portal deployment was timing out at 180s during rollout. Root causes: - HPA scales to 2 replicas but timeout only allowed 180s for both - .NET Blazor Server app needs significant startup time plus image pull - No startup probe meant liveness probe could kill slow-starting pods Changes: - Increase rollout status timeout from 180s to 600s - Add rolling update strategy (maxUnavailable: 0, maxSurge: 1) - Add startupProbe (30 attempts × 5s = 150s startup budget) - Remove initialDelaySeconds from liveness/readiness (startup probe handles this) https://claude.ai/code/session_01A95Uah18uxLJpuAR5HShNS
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adjusts the Portal’s AKS deployment behavior to reduce rollout failures caused by slow startup and multi-replica rollouts, aligning Kubernetes probe configuration and CI rollout waiting time with the Portal’s startup characteristics.
Changes:
- Increase the GitHub Actions
kubectl rollout statustimeout for the Portal from 180s to 600s. - Configure a RollingUpdate strategy for the Portal deployment (
maxUnavailable: 0,maxSurge: 1). - Add a
startupProbeand removeinitialDelaySecondsfrom existing liveness/readiness probes.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
src/portal/CloudHealthOffice.Portal/k8s/portal-deployment.yaml |
Adds RollingUpdate strategy and a startup probe; updates probe timing to rely on startupProbe gating. |
.github/workflows/deploy-azure-aks.yml |
Extends Portal rollout status wait time to 600s during deployment. |
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
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.
The portal deployment was timing out at 180s during rollout. Root causes:
Changes:
https://claude.ai/code/session_01A95Uah18uxLJpuAR5HShNS