Skip to content

nightly: leverage llm-d-modelservice assignment of priorityClassName#135

Open
maugustosilva wants to merge 1 commit intollm-d:mainfrom
maugustosilva:leverage_priority_class_from_modelservice
Open

nightly: leverage llm-d-modelservice assignment of priorityClassName#135
maugustosilva wants to merge 1 commit intollm-d:mainfrom
maugustosilva:leverage_priority_class_from_modelservice

Conversation

@maugustosilva
Copy link
Copy Markdown
Collaborator

@maugustosilva maugustosilva commented Apr 2, 2026

What does this PR do?

Version 0.4.9 of llm-d-modelservice allows the priorityClassName to be assigned directly on relevant kubernetes objects from the get go, therefore obviating the need for complex "patching with priorityClassName code we had previously"

Initially targeting only helmfile workflows.

IMPORTANT: this should not be merged until we update all guides with commented out priorityClassName for nightly CI/CD tests (llm-d/llm-d#1062)

Why is this change needed?

Reduces the need for custom code, increases maintainability and debuggability.

How was this tested?

  • Unit tests added/updated
  • Integration/e2e tests added/updated
  • Manual testing performed

Checklist

  • Commits are signed off (git commit -s) per DCO
  • Code follows project contributing guidelines
  • Tests pass locally (make test)
  • Linters pass (make lint)
  • Documentation updated (if applicable)

Related Issues

Version `0.4.9` of `llm-d-modelservice` allows the `priorityClassName`
to be assigned directly on relevant kubernetes objects from the get go,
therefore obviating the need for complex "patching with
`priorityClassName` code we had previously"

Initially targeting only `helmfile` workflows.

Signed-off-by: maugustosilva <maugusto.silva@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant