nodepool/releasenotes/notes/component-registry-327e1ade02155e39.yaml
James E. Blair a612aa603c Add the component registry from Zuul
This uses a cache and lets us update metadata about components
and act on changes quickly (as compared to the current launcher
registry which doesn't have provision for live updates).

This removes the launcher registry, so operators should take care
to update all launchers within a short period of time since the
functionality to yield to a specific provider depends on it.

Change-Id: I6409db0edf022d711f4e825e2b3eb487e7a79922
2022-05-23 07:41:27 -07:00

12 lines
457 B
YAML

---
upgrade:
- |
Due to an internal change in how Nodepool launchers communicate
with each other, all launchers should be upgraded to the same
version within a short period of time.
They will generally continue to work at different versions, but
the mechanism that allows them to yield to specific providers when
requested is being changed and so that will not function correctly
unless they are upgraded near-simultaneously.