jasonbrooks added a new comment to an issue you are following:
``
One of the benefits of modularity seems to be in allowing us to break out of the
traditional fedora versioning scheme, but the modules I've seen are built from fedora
packages, and those packages are tied to a particular fedora version. How will a
modularity-based atomic host, or module-based system containers for things like kubernetes
look/work different than what we have now?
For the containers case, I'd like to be able for, instance, to have a kubernetes
module that's installable on fedora atomic 25 or 26 that could track an arbitrary
number of upstream kube versions. Upstream kube is actively supporting 1.5.x 1.6.x and
1.7.x -- if we wanted to, we should be able to offer all of those, too. But would those
modules contain rpms built for a particular version of fedora, and would the container
images be based on a particular version of the base image? Or would there be some kind of
unmoored, continuous kube rpm and module-based base image?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/313