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

Equinix Metal - Add abbility to deploy servers with Layer 2/Hybrid networking #616

Closed
lgn87 opened this issue Jul 26, 2023 · 5 comments
Closed
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@lgn87
Copy link

lgn87 commented Jul 26, 2023

What would you like to be added (User Story)?

As a user of Cluster API it would be great to be able to lunch instances on Equinix Metal with Layer 2/Hybrid networking and to be able to specify custom set of private IPs for L2 interfaces.

Detailed Description

By default all servers that are created on Equinix Metal via Cluster API have Layer 3 networking and there is no option when provisioning Equinix Metal cluster to specify type of networking for instances or to create additional L2 interfaces with specific local IP addresses and VLAN.

It would be great to implement ability to specify following when provisioning Equinix Metal cluster:

  • Network type (L2/L3/Hybrid)
  • Creating network interfaces with specific VLAN
  • IP address range for L2 interfaces
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 26, 2023
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sbueringer
Copy link
Member

I think this issue should be opened in the repository of the Equinix Metal provider.

@killianmuldoon
Copy link

@lgn87 are you happy to close this issue and/or move it to the Equinix Metal provider repo? (I think this is the correct repo, but they've had a name change - https://github.com/kubernetes-sigs/cluster-api-provider-packet)

@sbueringer
Copy link
Member

Yup should be the right repo (checked the provider list in our book)

/transfer cluster-api-provider-packet

@k8s-ci-robot k8s-ci-robot transferred this issue from kubernetes-sigs/cluster-api Aug 3, 2023
@displague
Copy link
Member

duplicate of #613

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

5 participants