On Wed, Mar 20, 2019 at 02:03:57PM +0100, Thorsten Kukuk wrote:
Hi,
most of the time, pods/services/deployments for kubernetes have their source on github.com, the containers somewhere in a registry and you can deploy them using a yaml manifest on github.com, e.g. kubectl apply -f https://raw.githubusercontent.com/paulbouwer/hello-kubernetes/master/yaml/he...
Now we have already packaged some stuff, build a RPM from it in our buildservice, build a container from it in our buildservice, publish the container in our registry. How do we want to provide the manifest? We cannot point to OBS or an RPM. So my idea was, to build a sub-package, which contains the manifest with the adjusted image url pointing to our registry, install them by default on kubic and the user can use that to deploy the containers.
I have a related question. Where we should store the manifests before they get packaged? Some github repo? Only OBS? In my opinion it would be nice to have some repo like github.com/kubic/container-manifests with manifests to deploy some containers defined in github.com/kubic/container-images. And I would love to add a Cilium manifest there. Cheers, Michal -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org