News for hackers. Stuff that matters.
Re:K3s: Kubernetes without the features I don't care about by Serow225 on Thursday September 27, 2018 @01:06AM (#18082212)
I know pretty much zero about k8s, but was it really important to remove Swagger? Seems like relatively useful functionality and not a huge complexity point? I really like the idea of a simple opinionated K8s BTW good luck!
Re:K3s: Kubernetes without the features I don't care about by flurdy on Thursday September 27, 2018 @05:13AM (#18083017)
You can probably argue the same about every part removed, but if you (him) are not going to use it now, remove it.

Just dead weight otherwise. You can always add it later if people really need it.

True, Swagger docs can be helpful, but also if present but rubbish ignored swagger docs with missing features or side effects is more confusing. Just talk.

Re:K3s: Kubernetes without the features I don't care about by zeptomu on Thursday September 27, 2018 @06:53AM (#18083363)
Agreed. I don't really get the love for swagger, everything about it seems so meta. People say you get documentation for free, but auto generating some fancy webpage out of code (or the swagger spec) is not really documentation.

You have to write your documentation in a real human language. Maybe I just don't get the point of swagger.

Re:K3s: Kubernetes without the features I don't care about by felixfbecker on Thursday September 27, 2018 @04:33AM (#18082887)
Yeah this seems weird to me. If your API schema is not introspectable, where do your API clients come from? They don't grow on trees. I guess it's easy to cheat and just use an existing client, but that just shows that this is not a sustainable project