Template:

Networking Definition of Planned

Epic Template descriptions and documentation

Epic Goal

Extend the IPPool API to include the interface identifier (name or MAC) to IP reservations. We need want to use podNameSpace/pod/interface_id to identify an IP reservation. So a pod and its interface can always get the same IP when CNI_ADD is invoked to whereabouts when there is IP reservation record exists.

Why is this important?

This EPIC can help to resolve the long existing issue when STS pods are restarted after a node force reboot.

The current implementation doesn't reuse existing the IP for pods that has the same time. And it doesn't distinguish interfaces from the same pod either. This causes bugs like https://issues.redhat.com/browse/OCPBUGS-24663 and https://issues.redhat.com/browse/OCPBUGS-29648.

Planning Done Checklist

The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

• Priority+ is set by engineering
• Epic must be Linked to a +Parent Feature
• Target version+ must be set
• Assignee+ must be set
• (Enhancement Proposal is Implementable
• (No outstanding questions about major work breakdown
• (Are all Stakeholders known? Have they all been notified about this item?
• Does this epic affect SD? {}Have they been notified{+}? (View plan definition for current suggested assignee)
  1. Please use the "Discussion Needed: Service Delivery Architecture Overview" checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the "Discussion Needed: Service Delivery Architecture Overview" checkbox and record the outcome of the discussion in the epic description here.
  2. The guidance here is that unless it is very clear that your epic doesn't have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

Additional information on each of the above items can be found here: Networking Definition of Planned

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement
  details and documents.

...

Dependencies (internal and external)

1.

...

Previous Work (Optional):

1. https://redhat-internal.slack.com/archives/CFFSAHWHF/p1712841486339879
2. https://github.com/k8snetworkplumbingwg/whereabouts/pull/446

Open questions::

1. ...

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>