On Fri, Mar 22, 2019 at 05:37:51PM +0100, Thorsten Kukuk wrote:
We have different options and I think it depends on the maintainer. For a single file, I don't create a github repo, I maintain that in OBS. But we could create a github repo and collect different usefull manifests, and put them all in the same RPM. We have all options.
Yeah, I was thinking about having one repo for manifests. Especially for components which are not strictly parts of Kubernetes and are not deployed by kubeadm, but are going to be part of infra for many users - like CNI plugins (i.e. Cilium, multus), ingress controllers (i.e. traefik), Prometheus, Grafana, istio etc. We already have one blog post about traefik[0], but it has the deployment manifest pasted in the content and there is no link which can be simply used... And I'm thinking about writing a similar blog post about Cilium[1], so having the manifest on github repo and RPM packages would be nice. Cheers, Michal [0] https://kubic.opensuse.org/blog/2019-01-24-traefik/ [1] As soon as all my newest changes to Envoy and boringssl packaging will be released in Tumbleweed snapshot, I'm going to submit a container image to Kubic repo, then I would like to write that blog post. :) -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org