(Re-sending with the correct sender address) Am 22.03.19 um 16:45 schrieb Richard Brown:
On Wed, 20 Mar 2019 at 14:03, Thorsten Kukuk <kukuk@suse.de> 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 only would like to specify this, so that not everybody is using something else.
1. I think it should be easy to identify the RPM, so e.g. something like hello-kubernetes-<???>.rpm Which suffix could we use for this?
I would like us to use "$foo-k8s-yaml" as the pattern for this packaging naming
2. What would be a good location in the filesystem? /usr/share/defaults/manifests? One directory for everything? Every RPM having it's own directory?
I'd like us to use "/usr/share/k8s-yaml/$foo", with 1 directory for each RPM, but with the expectation that some packages will include multiple yaml examples
Yep. There will be packages with more than one yaml file:
https://github.com/rook/rook/tree/master/cluster/examples/kubernetes/ceph
Any ideas or opinions?
The -k8s-yaml packages must be installable on systems that don't have kubernetes installed, so they can be used for templating, integration with CI pipelines, or other use cases
Of course, some other packages might require -k8s-yaml packages in order for us to be able to execute them automatically when we want to do stuff like automated deployment of services to a kubic cluster
- Rich
For Rook, users are supposed to modify the yaml files and then apply them to the cluster. As long as we don't encourage users to modify the yaml files in place, everything should be fine? -- SUSE Linux GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nürnberg) -- SUSE Linux GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org