Skip to content

Enable changing the CIDR on shared networks when no IP ranges are defined #10459

Description

@borisstoyanov

The required feature described as a wish

As an admin I'd love to be able to change the CIDR of a shared network when there's no IP ranges defined. I appeaciate if there are VMs running they can end up on different CIDRs while on the same network, we want to avoid that. So my suggestion is to check if there are IP ranges defined, if no, this basically means there's no VMs on the network, at this stage this should allow the change of the CIDR, thoughts?

Activity

  1. adietrich-ussignal commented on Feb 25, 2025

    @adietrich-ussignal

    While I am very close to the original request, I think it only partially captures the desired behavior. I feel that having the ability to change the CIDR when one already exists is still a valid behavior that should be accounted for in this, given appropriate guardrails. I would think a CIDR change should also be permitted if no instances exist on said network. Accounting for the virtual router, either have the VR stop when this is performed, or require the operator to stop the VR before changing the CIDR on an existing shared network with a CIDR.

  2. locked and limited conversation to collaborators on Apr 10, 2025
  3. converted this issue into a discussion #10692 on Apr 10, 2025
  4. added this to the unplanned milestone on Sep 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions