Re: PROPOSAL: Shifting & Sharpening Focus - Putting MicroOS First
Hi, On Wed, May 04, Attila Pinter wrote:
After a quick chat yesterday I do see your point (https://t.me/openSUSE_MicroOS_Desktop/14845). The only thing I would miss from a k3s-MicroOS system is kubicctl which IMO really gives the edge over other k8s distributions.
kubicctl is just a wrapper parsing kubectl output and calling the action on all nodes via salt. Shouldn't be to hard to implement that for k3s, fork the project and adjust the code. And if the k3s output is not really parseable, open a feature request for k3s. But I have no time for that, there are other projects like MicroOS TIU ;) which eats up my time. And if it is about the system roles for kubic-control: that should be easy adjustable, if necessary at all. Thorsten
If the project does reach EOL I would be quite happy to work on a similar solution for MicroOS and k3s. If, however, the contributors of the project decide to keep it alive, and maintain it I would be also happy to help. Although I have very little experience with openSUSE tools (which is shameful at this point really) I'm happy to learn.
Either way I respect your decision, and gladly help out wherever I can.
Br, A.
-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Ivo Totev (HRB 36809, AG Nürnberg)
------- Original Message -------
On Wednesday, May 4th, 2022 at 1:40 PM, Thorsten Kukuk
Hi,
kubicctl is just a wrapper parsing kubectl output and calling the action on all nodes via salt. Shouldn't be to hard to implement that for k3s, fork the project and adjust the code. And if the k3s output is not really parseable, open a feature request for k3s.
With your blessing would be happy to look into it. -- Br, A.
participants (2)
-
Attila Pinter
-
Thorsten Kukuk