Skip to content

manifests: requests and 5 s probes for the two remaining BestEffort pods - #2955

Open
Davanum Srinivas (dims) wants to merge 1 commit into
agent-substrate:mainfrom
dims:control-plane-probe-shape
Open

Davanum Srinivas (dims) wants to merge 1 commit into
agent-substrate:mainfrom
dims:control-plane-probe-shape

Conversation

@dims

Copy link
Copy Markdown
Collaborator

ate-idp-server and podcertificate-controller run BestEffort, and the idp server's probes use the default 1 s timeout. On a node packed with sandboxes a BestEffort pod gets almost no CPU. One idp replica missed three liveness probes while the node's sandboxes were tearing down, and kubelet restarted it with nothing wrong in the process. #2557 gives the other control-plane pods requests and 5 s probes; these two were left out.

Change.

  • ate-idp-server: requests 50m / 128Mi, and both probes get timeoutSeconds: 5 with failureThreshold: 6.
  • podcertificate-controller: requests 50m / 128Mi. It has no probes.

Tests. Manifests only. The base and kind overlays render as the installer builds them, with the new fields on the idp Deployment; the installer's tests pass; the e2e jobs deploy the result.

  • Tests pass
  • Appropriate changes to documentation are included in the PR (none needed)

@dims
Davanum Srinivas (dims) force-pushed the control-plane-probe-shape branch 2 times, most recently from b9241af to 3baef7c Compare October 20, 2026 11:17
@dims
Davanum Srinivas (dims) marked this pull request as ready for review October 20, 2026 13:31
@dims
Davanum Srinivas (dims) force-pushed the control-plane-probe-shape branch 9 times, most recently from 95086d1 to a66d786 Compare October 27, 2026 12:34
@bowei Bowei Du (bowei) added area/dev-infra area/identity area/reliability area/security Security related issue/pr kind/bug Something isn't working / bugfixes labels Oct 27, 2026
ate-idp-server and podcertificate-controller ran BestEffort, and the
idp server's probes used the default 1 s timeout. On a node packed with
sandboxes such a pod gets almost no CPU: an idp replica missed three
liveness probes and was restarted with nothing wrong in it. Give both
the CPU and memory requests the other control-plane pods have, and the
idp server a 5 s probe timeout with a failure threshold of 6.

Signed-off-by: Davanum Srinivas <davanum@gmail.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/dev-infra area/identity area/reliability area/security Security related issue/pr kind/bug Something isn't working / bugfixes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants