You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added:
Public nodeadm versioning of some kind. There are several options that can be left up to the implementation.
releases within this repository (with a bundled version of nodeadm)
split nodeadm its own repository, releases within the new repo
Why is this needed:
Its not clear how nodeadm is built and bundled into the public AMIs. Downstream consumers (e.g. [0]) cannot determine how to bundle nodeadm because its right source code to build against is not labeled. Initial searches point to platform9/nodeadm, which isn't the right version.
The text was updated successfully, but these errors were encountered:
rpocase
changed the title
explicitly versioning of nodeadm that should be used in EKS AMIs
explicit versioning of nodeadm that should be used in EKS AMIs
May 6, 2024
What would you like to be added:
Public nodeadm versioning of some kind. There are several options that can be left up to the implementation.
Why is this needed:
Its not clear how nodeadm is built and bundled into the public AMIs. Downstream consumers (e.g. [0]) cannot determine how to bundle nodeadm because its right source code to build against is not labeled. Initial searches point to platform9/nodeadm, which isn't the right version.
[0] - https://bugs.launchpad.net/cloud-images/+bug/2058610
The text was updated successfully, but these errors were encountered: