Open Timoses opened 2 years ago
Thank you for your contributions. Noticed that this issue is idle since 180 days! There is a possibility that this issue is already fixed in later releases. Please upgrade and check! If I don't hear any update in this issue in next 2 weeks, will be closing the issue. That doesn't mean one can't re-open the issue! Just comment on the issue, and click 'Reopen', if you still have the issue.
I think this should be still relevant in order to make Kadalu more secure (prevent large attack surface on kadalu productive containers).
Thank you for your contributions. Noticed that this issue is idle since 180 days! There is a possibility that this issue is already fixed in later releases. Please upgrade and check! If I don't hear any update in this issue in next 2 weeks, will be closing the issue. That doesn't mean one can't re-open the issue! Just comment on the issue, and click 'Reopen', if you still have the issue.
I think this should be still relevant in order to make Kadalu more secure (prevent large attack surface on kadalu productive containers).
Still same I suppose.
Still same I suppose.
- agreed and at the same time I want to have this as a feature (with Moana) rather than some hacky workaround now
- Pardon for making you to keep this issue alive and thanks as well for being around 😅
Is your feature request related to a problem? Please describe. Currently kubectl is included in the builder base image. From a security standpoint the images providing the actual work should be as lean as possible.
Furthermore, there exist arguments that users should be allowed to use a kadalu pod as a "base of operations" to execute kubectl commands including access to the
kubectl kadalu
plugin. This blocks direct building of images (#839).Describe the solution you'd like Provide a separate toolbox container/pod (e.g. like rook's toolbox). Perhaps even the
kubectl kadalu
tool itself can be used to manage this.Describe alternatives you've considered /
Additional context /