Should the rukpakctl executable be removed from the core container image
Currently, the rukpakctl executable is packaged with the runtime components for rukpak which inflates the total size of the container image. We can investigate removing it, and releasing it as a standalone binary during the release pipeline.
This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.
Removing the /lifecycle/stale label as we should remove the binary from the image if it isn't used by a running RukPak deployment.