Conversation
Remove documentation for CurrentAlloc, Allocation, and LoadProfile types that were removed in PR #553 as part of the model-based scaling cleanup. Changes: - Remove Allocation and LoadProfile type definitions from CRD reference - Remove currentAlloc field from VariantAutoscalingStatus documentation - Update status examples to use desiredOptimizedAlloc instead - Update VariantAutoscalingStatus description to reflect current state These types were part of the model-based scaling implementation and are no longer needed for saturation-based scaling.
asm582
approved these changes
Jan 9, 2026
github-actions bot
pushed a commit
that referenced
this pull request
Jan 9, 2026
- Update VariantAutoscalingStatus godoc comment to remove mention of 'current allocation' - Add clarifying notes to HPA and KEDA integration docs about log format changes - Mark debug log examples as illustrative from older model-based scaling version Follow-up to PR #554 which removed Allocation types from CRD reference docs.
3 tasks
ev-shindin
pushed a commit
to ev-shindin/workload-variant-autoscaler
that referenced
this pull request
Jan 14, 2026
…tion-api-references-a292c5d0430359d8 docs: Remove references to deprecated Allocation API types
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
1 participant
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
This PR updates documentation to reflect the API changes made in PR #553, which removed the
AllocationandLoadProfiletypes from the VariantAutoscaling API as part of the model-based scaling cleanup.Changes Made
Removed Documentation
accelerator,numReplicas,maxBatch,itlAverage,ttftAverage, andloadarrivalRate,avgInputTokens, andavgOutputTokensVariantAutoscalingStatusdocumentationUpdated Examples
currentAllocationwithdesiredOptimizedAllocin status examplesFiles Modified
docs/user-guide/crd-reference.md- Removed Allocation and LoadProfile type definitions, updated VariantAutoscalingStatusdocs/user-guide/configuration.md- Updated status examplesdocs/design/controller-behavior.md- Updated deployment deletion status examplesContext
These types were part of the model-based scaling implementation that tracked detailed allocation metrics (ITL, TTFT, batch size, load characteristics). With the shift to saturation-based scaling as the primary autoscaling approach, these fields are no longer part of the API surface.
The internal
interfaces.Allocationtype still exists for internal use by the optimizer and model analyzer components, but is not exposed in the Kubernetes API.Verification
Related