Repository navigation
docs: run SDK workers on Kubernetes with explicit shutdown - #393
Merged
Merged
Conversation
|
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.
Deploy application SDK workers separately from the Server's Laravel queue worker. This adds a minimal Deployment with the actual raw-manifest Service URL, external TLS guidance, a Secret reference, unique Pod worker IDs, replica/resources examples and per-SDK SIGTERM/cleanup instructions. Refs #336.
Product review remains the existing accepted documentation/deployment gap. Published-source review confirms distinct lifecycle contracts: PHP managed run with pcntl, Python explicit signal wiring plus stop/run-task and shared drain deadline, and Rust Unix SIGTERM supplied to run_until. A manifest must not conceal a missing drain or promise that forced termination undoes side effects.
All eight guides and all seven reviewed-source hashes are included. Executable blocks match English exactly. Draft: actual Kubernetes acceptance is pending. The focused workflow builds normal published PHP3.4.1, Python2.9.0 and Rust4.7.0 SDK applications, checks package identities, uses a locked Rust registry graph and HTTPS-only verified tool downloads, extracts the guide's actual Deployment, and exercises registration, real workflow/activity completion, idle SIGTERM and deregistration against the immutable published Server2.11.0 image. This is its own bounded guide-acceptance cohort, not promotion of the selected compatibility tuple, a production Server/HA installation, or a source overlay.
Local Python fixture syntax and whitespace checks pass. PHP syntax passed with the published PHP8.3.35 CLI image. The local Cargo metadata-only resolution used the published Rust1.90 image, verified the4.7.0 registry checksum and retired its temporary container/cache without compiling locally. Required all-locale CI, package/runtime acceptance, Sonar review, actual Pages publication and live checks precede delivery. No Cloud, Server, SDK or shared protocol source is changed.
Exact head4faac223522656d9c6eb69a641214e41ba26ae8c passes all8 CI39968613613 and actual published-artifact Kubernetes run39968613525: three completed workflows/activities, six Pod worker IDs, six successful idle SIGTERM shutdowns and confirmed deregistrations. All checks pass, Sonar0/0/0. Earlier failed fixture attempts are preserved in the owning issue; no runtime product fix is inferred. Pages/live acceptance remains before Website closure.
Delivery complete: normal merge2a07fcb9c9; site artifact39972508095 and actualPages39975647870 pass. All8 live routes/actual copied qualified YAML/fullmetadata/TOC/localized rollout links/64 exact-source paragraphs and en/ja/zh390px light/dark views verified. Website336 is complete; the focused runtime qualification retains idle-only/ephemeral-SQLite scope and all original failures.