Repository navigation
Conversation
On first boot, asapd-lite configures all eight ConnectX-8 ports and sets up DOCA PCC before /healthz starts serving. This can run past the 60 second liveness window, so kubelet kills the container with exit code 143 and setup starts over. In a 16-node A4X Max test on Ubuntu 26.04 nodes, kubelet killed 9 of 12 asapd-lite pods this way Add a startupProbe on the same /healthz endpoint that gives setup up to 10 minutes (60 checks, 10 seconds apart) to finish. The liveness and readiness probes are unchanged and start once the startup probe passes
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.
On first boot, asapd-lite configures all eight ConnectX-8 ports and sets up DOCA PCC before
/healthzstarts serving. This can run past the 60 second liveness window, so kubelet kills the container (exit code 143) and setup starts over. In a 16-node A4X Max test on Ubuntu 26.04 nodes, kubelet killed 9 of 12 asapd-lite pods this way. The GKE A4X Max guide has userskubectl applythis manifest directly, so they can hit the same restartsstartupProbeon/healthzport 19540 withperiodSeconds: 10andfailureThreshold: 60, which gives setup up to 10 minutes to finishlivenessProbeandreadinessProbeas they are. Kubernetes holds them until the startup probe passes