Skip to content
This repository has been archived by the owner on Aug 12, 2024. It is now read-only.

Should the rukpakctl executable be removed from the core container image #507

Open
timflannagan opened this issue Aug 19, 2022 · 2 comments
Open

Should the rukpakctl executable be removed from the core container image #507

timflannagan opened this issue Aug 19, 2022 · 2 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
backlog

Comments

@timflannagan
Copy link
Contributor

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.
@timflannagan timflannagan changed the title Consider removing the rukpakctl executable from the container image Should the rukpakctl executable by removing from the core container image Aug 19, 2022
@timflannagan timflannagan added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Aug 24, 2022
@timflannagan timflannagan added this to the backlog milestone Aug 24, 2022
@github-actions
Copy link

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.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 24, 2022
@awgreene awgreene changed the title Should the rukpakctl executable by removing from the core container image Should the rukpakctl executable be removed from the core container image Nov 17, 2022
@awgreene
Copy link
Member

Removing the /lifecycle/stale label as we should remove the binary from the image if it isn't used by a running RukPak deployment.

@awgreene awgreene added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
backlog
Development

No branches or pull requests
2 participants
@awgreene @timflannagan