feat(api7): support timeoutSeconds for probes (3.9.x) - #357
Open
AlinsRan wants to merge 1 commit into
Open
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
…er/developer-portal/api-usage probes livenessProbe and readinessProbe for these components previously only exposed initialDelaySeconds, periodSeconds, and failureThreshold, so timeoutSeconds always fell back to Kubernetes' default of 1s and could not be tuned for slow-starting deployments.
AlinsRan
force-pushed
the
feat/api7-probe-timeout-3.9
branch
from
August 26, 2026 09:39
717a5f9 to
b53898e
Compare
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.
Summary
Backport of #356 to the
release/3.9chart line.dashboard,dp_manager,file_server,developer_portal, andapi_usagelivenessProbe/readinessProbe only exposedinitialDelaySeconds,periodSeconds, andfailureThreshold, sotimeoutSecondsalways fell back to Kubernetes' default of 1s and was not configurable.timeoutSecondstovalues.yaml(default1, matching prior implicit behavior) and wire it through the corresponding Deployment templates for all five components.charts/api7/README.mdviamake helm-docsand bumped the chartversion(3.9.5 -> 3.9.6);appVersionunchanged since this is chart-only.Test plan
helm lint charts/api7helm template charts/api7and confirmedtimeoutSeconds: 1renders by default for all five probes