Template:

Networking Definition of Planned

Epic Template descriptions and documentation

Epic Goal

In a few releases there is a plan to ship OCP with support for both RHCOS 9 and 10. This is going to have significant impacts for the on-prem networking components because we are so tightly tied to the underlying OS. A couple of immediate concerns come to mind:

• Much more testing required because now anything that interacts with the host needs to be tested twice. Probably not double (CoreDNS, for example, probably doesn't need both a 9 and 10 test job), but still significant.
• We'll need to figure out how to handle Kubernetes-NMState versioning. Having mismatches between the host NetworkManager version and the library in the KNMState image has caused us problems in the past, so we'll need to figure out how to avoid/address that.
• The HAProxy monitor uses the host iptables binary to manage firewall rules. While we won't be using iptables by then, the same basic problem of interacting with the host firewall will still exist.

I would be surprised if there aren't other issues I haven't considered too, but this is enough to make it clear significant effort will be required to implement this.

Why is this important?

The product has decided to do this and in order for our components to keep working we have no choice but to figure it out. While this isn't our top priority as of this writing, it will be a blocker issue for whatever release we end up shipping dual RHCOS support in.

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. …

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>