Configurable options to API server about kubernetes-the-right-way HOT 5 CLOSED

As much as I like the idea of the ability to customise, I think to a certain extent it just adds too much complexity. The goal has always been to keep it simple and leave keep specific configuration away from this project.

from kubernetes-the-right-way.

Yeah, that's fair enough! How would you suggest tweaking the configuration? I'd very much like to keep using KTRW. I could fork this repository, but that feels bad as well.

from kubernetes-the-right-way.

I would include install.yml in a top-level playbook that would do stuff before and after running ktrw. Look at test/main.yml which does exactly this.

https://github.com/amimof/kubernetes-the-right-way/blob/master/test/main.yml#L109

from kubernetes-the-right-way.

Hmm, that could work. However, that means I have to replicate the service file for kube-apiserver. That could potentially cause conflicts with future versions of KTRW.

I made a small PR with a suggestion that I don't think is too complex and allows very dynamic configuration, in an easy way. What do you think? See #38.

from kubernetes-the-right-way.

Decided to fork the repository after all, and try to keep up with your changes in the future. :)

Closing this!

from kubernetes-the-right-way.