From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH container 1/1] Signed-off-by: Maurice Klein <klein@aetherus.de>
Date: Mon, 19 Jan 2026 15:35:35 +0100 [thread overview]
Message-ID: <021b748f-44db-4546-8399-c6f7312a11fc@proxmox.com> (raw)
In-Reply-To: <mailman.420.1768811863.353.pve-devel@lists.proxmox.com>
Hi!
Thanks for your contribution, did you already check out our guidelines
[1] [2] and send a signed CLA? Without it, we cannot accept any
contributions.
I've looked at the proposal, but I wanted to take some time to think
more about the general concept. It seems like you want to build
something similar to current Kubernetes networking solutions that
utilize BGP but without the whole EVPN / VXLAN stuff?
Maybe it'd make more sense to discuss about how we could improve the
EVPN zone or SDN in general to make such setups easier - potentially a
new zone that is something of an inbetween of the simple zone and EVPN
zone could make sense. In any case, I think removing the bridge and
implementing it this way is the wrong way to go about this.
[1] https://www.proxmox.com/en/about/open-source/developers
[2] https://pve.proxmox.com/wiki/Developer_Documentation
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2026-01-19 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260109121049.70740-1-klein@aetherus.de>
2026-01-09 12:10 ` Maurice Klein via pve-devel
[not found] ` <20260109121049.70740-2-klein@aetherus.de>
2026-01-19 8:37 ` Maurice Klein via pve-devel
2026-01-19 14:35 ` Stefan Hanreich [this message]
[not found] <20260109124514.72991-1-klein@aetherus.de>
2026-01-09 12:45 ` Maurice Klein via pve-devel
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=021b748f-44db-4546-8399-c6f7312a11fc@proxmox.com \
--to=s.hanreich@proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.