Jiaxin Shan

Hi @kiriloman, autoscaler needs to be specified in the yaml. check this example out. Do you think following doc helpful? If not, feel free to share your thoughts and we...

Great to see the proposal! We are doing experiments to offload reusable KV contents to external cache store. Happy to discuss more details.

Agree. it used to have GHCR build https://github.com/vllm-project/aibrix/blob/fcc08964982c59cb9e3d4a9acb6634c9ab7741f8/.github/workflows/docker-push-images.yml#L39-L46 After we transferred the repo, it doesn't have package write permission. We can resolve this issue either adopting previous orgs or ask...

Option 1: We can ask vLLM repo's `write:package` permission, but the trick thing is it doesn't have namespace to use. for example, the controller-manager image becomes `ghcr.io/vllm-project/controller-manager:v0.3.0` instead of `ghcr.io/vllm-project/aibrix/controller-manager:v0.3.0`....

 Need to change the scope here. 

Seems there's no easy way to grant the access. I will create a personal access token just with write:packages permission and use it as `AIBRIX_ORG_PACKAGE_UPDATE_GITHUB_TOKEN` scope: - write:packages - read:packages...

 classic token has been disabled. The trick thing is  ref: - https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry#authenticating-to-github-packages - https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#personal-access-tokens-classic

then we have to re-enable classic tokens  

 Update: 

https://github.com/vllm-project/aibrix/actions/runs/14801263519/job/41567850682 job pass and we can close this story.