Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support different cloud-init network-config #94

Open
mcbenjemaa opened this issue Jan 28, 2024 · 2 comments
Open

Support different cloud-init network-config #94

mcbenjemaa opened this issue Jan 28, 2024 · 2 comments
Labels
enhancement New feature or request kind/feature

Comments

@mcbenjemaa
Copy link
Member

mcbenjemaa commented Jan 28, 2024

Describe the solution you'd like

Currently we only support network-config version 2 which supports netplan distributions.

We need a way of making this configurable so the user can choose which network-config version to use.

Anything else you would like to add:

This will make sure capmox supports various distributions

@65278
Copy link
Collaborator

65278 commented Apr 24, 2024

This is a can of worms, we support features which are not supported by cloudinit network-config version 1, so we can't just naively convert with a different template. In fact, we only support netplan passthrough.
If we decide to support this, at the very least we need to document features which will not work.

@65278
Copy link
Collaborator

65278 commented Jun 10, 2024

Some thoughts: since this is a "per proxmox template" issue, we can't make this a controller environment variable. The information of what renderer to use would need to live in the proxmox machine templates themselves (as they reference templateID).
An optional variable here could allow us to call a different renderer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request kind/feature
Projects
None yet
Development

No branches or pull requests

2 participants