Greetings, *TL;DR *- There will be no upgrade path due to incompatible changes from cs:trusty/etcd to cs:xenial/etcd. Please be prepared for re-deployment if an upgrade is required.
As some of you may know, we have been toiling quite hard on the Etcd charm this last month, adding TLS encryption for an "SSL Everywhere" experience. Read: End to End encryption on our Kubernetes bundle. This brought with it a lot of upgrade concerns, and we have not yet landed the changes in the stable channel. This was by design so we could evaluate the potential impact on existing clusters of Etcd deployed with Juju. It's become quite apparent to us that there is a very convoluted upgrade path. And this upgrade path is a one-time scenario, that will require an engineering effort that doesn't cover its use. With that being said, we're now settled on breaking compatibility on the series boundary of Xenial forward. Meaning when you deploy etcd from Xenial onward, TLS will be enabled by default, and we are dropping trusty as a supported series moving forward. This leaves users of the older etcd charm(s) in a very well understood behavior, and they will not be prompted for an update that would potentially break their existing deployments. We wanted the community to be well aware of the plan moving forward so there are no surprises, and will continue to strive towards a stellar user experience. If you have any questions, comments or concerns, please feel free to reply to this thread and continue the conversation. All the best, Charles -- Juju Charmer Canonical Group Ltd. Ubuntu - Linux for human beings | www.ubuntu.com Juju - The fastest way to model your service | www.jujucharms.com
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
