Goal

Play with the concept of self-service overlay networks and come up with a simple teaser for potential users and a PoC for CNV-35223.

User Stories

• As a cluster admin,
  I want developers to be able to create additional networks themselves,
  so they don't bother me unnecessarily,
  but only if these networks cannot be abused to gain access to other unavailable networks or exhaust cluster resources they would not be able to exhaust otherwise.
• As a developer, I want to request and quickly obtain an overlay network for my project by myself.
• As a developer, I want to delete an overlay network in my project.

Non-Requirements

• While CRDs will be the preferred way to support this in production, this PoC does not have to define a new one. Instead it may stick to ConfigMaps.
• Since the on-demand networks should be safe (see the acceptance criteria), this feature does not have to be feature-gated.
• This feature should be but does not have to be shipped with downstream CNV. Consider it while phasing the work.
• We can use the Kind cluster from to get a development environment https://github.com/openshift/ovn-kubernetes

Notes

• ...