fleet deprecation, removal from Container Linux by 2018-02-01

151 views
Skip to first unread message

j...@coreos.com

unread,
Feb 17, 2017, 5:56:38 PM2/17/17
to CoreOS User

As we announced last week, [CoreOS will remove the fleet cluster scheduling software from Container Linux on February 1, 2018, and support for fleet will end at that time][1]. fleet is effectively in maintenance mode, receiving only security updates and bug fixes as of February, 2017. This move reflects our focus on Kubernetes and Tectonic for cluster orchestration and management. It simplifies the deployment picture for users while delivering an automatically updated Container Linux operating system of the absolute minimum surface and size.


New cluster deployments should be using

  • CoreOS [Tectonic][2] for production Kubernetes clusters backed by expert support and turnkey deployments and updates, or

  • Open source [Kubernetes on Container Linux][3], or

  • Open source [minikube][4] for a first look at Kubernetes on your laptop.


After February 1, 2018, a fleet container image will continue to be available from the CoreOS Quay registry, but will not be shipped as part of Container Linux. [Admins who want to keep using fleet can use the container image and wrapper script to run fleet][5].


Current fleet users with [Container Linux Support][6] can get help with migration from their usual support channel until the final deprecation date. fleet users should check out the [fleet to Kubernetes webinar with CoreOS CTO Brandon Philips][7] for details about differences between the two systems and advice on planning for migrating or maintaining existing fleet clusters. CoreOS engineers and community members will be ready to discuss fleet issues on this mailing list and in the [CoreOS IRC channel][8].


[1]: https://coreos.com/blog/migrating-from-fleet-to-kubernetes.html

[2]: https://coreos.com/tectonic

[3]: https://coreos.com/kubernetes/docs/latest/

[4]: https://github.com/kubernetes/minikube

[5]: https://coreos.com/fleet/docs/latest/launching-containers-fleet.md#running-fleet-via-ignition

[6]: https://coreos.com/products/premium-managed-linux/

[7]: https://www.brighttalk.com/webcast/14601/245545

[8]: irc://irc.freenode.org:6667/#coreos



Juan Laporte

unread,
Aug 24, 2018, 4:41:17 PM8/24/18
to CoreOS User
Which is the last stable release version to contain Fleet and which stable version release was it removed? I need to update my cluster but do not want all my services to go down due to fleet being remove via the update...

regards

David Michael

unread,
Aug 24, 2018, 4:54:09 PM8/24/18
to Juan Laporte, CoreOS User
On Fri, Aug 24, 2018 at 4:41 PM, Juan Laporte <awat...@gmail.com> wrote:
> Which is the last stable release version to contain Fleet and which stable
> version release was it removed? I need to update my cluster but do not want
> all my services to go down due to fleet being remove via the update...

It was removed in 1675, so 1632.3.0 would have been the last stable
release with it.

Using a release that old is a bad idea due to all the missing security
fixes (Spectre v2, FragmentSmack, L1TF, etc., see
https://coreos.com/releases/), so it would be preferable if you could
try running fleet in a container on the latest version:

https://raw.githubusercontent.com/coreos/fleet/master/scripts/fleet-wrapper

Note that will also require a PolicyKit rule in /etc/polkit-1/rules.d:

https://raw.githubusercontent.com/coreos/coreos-overlay/4ae082f9d8c6f740bc3d63aa505d35fec9fb8887/app-admin/fleet/files/98-fleet-org.freedesktop.systemd1.rules

Thanks.

David
Reply all
Reply to author
Forward
0 new messages