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

Get Submariner/OVN-Kubernetes Integration to a Production Ready State #96

Closed
8 of 28 tasks
astoycos opened this issue Mar 28, 2022 · 4 comments
Closed
8 of 28 tasks

Comments

@astoycos
Copy link
Contributor

astoycos commented Mar 28, 2022

Epic Description

OVN-Kubernetes is one of the two CNI's supported by RedHat Openshift, and will soon become the sole CNI for the Kubernetes distribution. Submariner supports the CNI via the OVN-Kubernetes specific NetworkPluginSyncer, however the design is more of a POC and currently non-functional with recent OVN-K versions. Many more steps need to be taken in order to ensure the integration is bug-free and ready for production environments, this epic will track the work that is needed to get the integration to such a state.

Acceptance Criteria

Submariner's ability to connect clusters utilizing the OVN-Kubernetes CNI is 100% functional with current OVN-K builds, and the correct CI infrastructure has been put into place in order to ensure the continued functionality of the integration.

Definition of Done (Checklist)

  • Code complete
  • Relevant metrics added
  • The acceptance criteria met
  • Unit/e2e test added & pass
  • CI jobs pass
  • Deployed using cloud-prepare+subctl
  • Deployed using ACM/OCM addon
  • Deploy using Helm
  • Deployed on supported platforms (for e.g kind, OCP on AWS, OCP on GCP)
  • Run subctl verify, diagnose and gather
  • Uninstall
  • Troubleshooting (gather/diagnose) added
  • Documentation added
  • Release notes added

Work Items

@sridhargaddam
Copy link
Member

The following PR implements the necessary support for OCP 4.11 - submariner-io/submariner#1689

@nyechiel
Copy link
Member

@vthapar @sridhargaddam can you please review the issues linked to this epic? is there anything we want to still target to 0.13?

@maayanf24
Copy link
Contributor

@vthapar @sridhargaddam - can you report individual issues to track the remaining work and close the epic?

@nyechiel
Copy link
Member

Closing now that 0.13 was shipped. Other gaps (e.g, Globalnet support) should be tracked separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants