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

Add support for HCN v2 endpoint and add unit tests #2343

Conversation

katiewasnothere
Copy link
Contributor

  • switch to HCN v2 endpoint API by default
  • Support parsing routes in GCS when we setup the network interfaces
  • [breaking] update gcs bridge LCOW network adapter type with new fields that better align with v2 endpoint
  • Add unit tests for new GCS side changes
  • Add support for the legacy policy based routing with the new endpoint type
    The motivation for this change was to support adding custom routes on interfaces. However, the v1 endpoint implementation does not have this support. Therefore, we needed to move to the V2 implementation.

* switch to HCN v2 endpoint API instead of HNS v1 endpoint API
* Support parsing routes in GCS when we setup the network interfaces
* [breaking] update gcs bridge LCOW network adapter type with new fields that better
align with v2 endpoint
* Add unit tests for new GCS side changes

Signed-off-by: Kathryn Baldauf <kabaldau@microsoft.com>
Signed-off-by: Kathryn Baldauf <kabaldau@microsoft.com>
Copy link

@rawahars rawahars left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚢

Signed-off-by: Kathryn Baldauf <kabaldau@microsoft.com>
@katiewasnothere katiewasnothere force-pushed the user/kabaldau/lcow_hns_v2_endpoint_and_v1 branch from 5190038 to 262f05c Compare January 14, 2025 17:48
@katiewasnothere katiewasnothere merged commit 8d81359 into microsoft:main Jan 15, 2025
19 checks passed
@katiewasnothere katiewasnothere deleted the user/kabaldau/lcow_hns_v2_endpoint_and_v1 branch January 15, 2025 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants