Implement Wasm autoscaler policy controller logic#4299
Implement Wasm autoscaler policy controller logic#4299markmandel merged 1 commit intoagones-dev:mainfrom
Conversation
|
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
|
Build Succeeded 🥳 Build Id: d7ad11ea-1a1e-4649-84e0-80930bb9fab5 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version: |
lacroixthomas
left a comment
There was a problem hiding this comment.
Looking great !
I'm not sure about the "limited" part, if there should also be something to prevent going over a max value ? Or we expect that they handle it from their wasm ? 🤔
(also, the joy of the vendors hehe)
Actually about the limited part, they could use another policy 👌🏼 |
Add controller implementation for Wasm-based fleet autoscaling: - Implement applyWasmPolicy function to execute Wasm modules for autoscaling decisions - Add Wasm plugin lifecycle management with proper initialization and cleanup - Integrate Extism SDK for Wasm module loading and execution - Support plugin configuration and hash verification - Add FleetAutoscaleReview request/response handling for Wasm plugins - Include comprehensive unit tests for Wasm policy functionality - Add vendor dependencies: Extism SDK, Wazero runtime, Observe SDK, and OpenTelemetry proto Work on agones-dev#4080
I think I know what you're saying -- but just to be sure. The wasm policy matches the webhook autoscaler policy, in that there's no specified maximum Agones is aware of (but there could be behind the scenes from the webhook or wasm -- that's up that implementation). Before I merge, does this line up with your expectations and understanding? |
bf2e78d to
af20e92
Compare
|
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
|
Build Failed 😭 Build Id: 923d9cdd-38fd-442a-b0a0-600f72abe8b7 Status: FAILURE To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Yep all good 👌🏼 |
|
Huh this one again 🤔 Maybe there's a cluster update happening. |
|
/gcbrun |
|
Build Succeeded 🥳 Build Id: 941a5b53-9676-4058-8c15-dcf163a4d7e2 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version: |
Add controller implementation for Wasm-based fleet autoscaling: - Implement applyWasmPolicy function to execute Wasm modules for autoscaling decisions - Add Wasm plugin lifecycle management with proper initialization and cleanup - Integrate Extism SDK for Wasm module loading and execution - Support plugin configuration and hash verification - Add FleetAutoscaleReview request/response handling for Wasm plugins - Include comprehensive unit tests for Wasm policy functionality - Add vendor dependencies: Extism SDK, Wazero runtime, Observe SDK, and OpenTelemetry proto Work on agones-dev#4080
What type of PR is this?
/kind feature
What this PR does / Why we need it:
Add controller implementation for Wasm-based fleet autoscaling:
Which issue(s) this PR fixes:
Work on #4080
Special notes for your reviewer:
Next will be e2e tests with the feature flags moved to alpha -- then also docs!