From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
"DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
Subject: Re: [pve-devel] fosdem talk: k8s CRIU live migration support
Date: Tue, 14 Feb 2023 10:26:28 +0100 [thread overview]
Message-ID: <4901bf27-7a24-363c-caf6-6d1d656bc053@proxmox.com> (raw)
In-Reply-To: <7be3bb25fa56e912b199ec4c4050134168c50d6f.camel@groupe-cyllene.com>
On 12/02/2023 10:16, DERUMIER, Alexandre wrote:
>
> It seem than k8s finally support CRIU live migration
>
> https://fosdem.org/2023/schedule/event/container_kubernetes_criu/
>
interesting
>
> I don't known about lxc, but maybe is it finally working too ?
with a limited feature set maybe, aren't k8s often very minimal, i.e.,
not even having local storage support and a lot of other restrictions
that the service mesh architecture brings with it.
As kernel features always change it's a moving target, which is one of
the main reasons we never tried to push (hard) for it.
But retrying and checking out the current state with current CRIU, LXC
and Kernel is definitively worth a try - if only to document what's
still missing for a PVE integration.
prev parent reply other threads:[~2023-02-14 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 9:16 DERUMIER, Alexandre
2023-02-14 9:26 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4901bf27-7a24-363c-caf6-6d1d656bc053@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=Alexandre.DERUMIER@groupe-cyllene.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox