Skip to content

Conversation

@ramiro-gamarra
Copy link
Contributor

Reason for Change:

In order to communicate the availability zone for ncs from the virtual machine where they are placed, we first need to expand the nnc definition to include the az in its status. Population will be handled in a subsequent PR.

Issue Fixed:

Requirements:

Notes:

@ramiro-gamarra ramiro-gamarra requested a review from a team as a code owner October 29, 2024 17:42
Copy link
Collaborator

@thatmattlong thatmattlong left a comment

Choose a reason for hiding this comment

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

let's make the az property optional

@ramiro-gamarra ramiro-gamarra force-pushed the add-availability-zone-to-nnc branch from 090bbca to 05f5411 Compare October 30, 2024 16:32
@ramiro-gamarra
Copy link
Contributor Author

/azp run Azure Container Networking PR

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ramiro-gamarra ramiro-gamarra added this pull request to the merge queue Oct 30, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 30, 2024
@paulyufan2 paulyufan2 added this pull request to the merge queue Oct 31, 2024
Merged via the queue into master with commit 19156a7 Oct 31, 2024
14 checks passed
@paulyufan2 paulyufan2 deleted the add-availability-zone-to-nnc branch October 31, 2024 16:21
sivakami-projects pushed a commit that referenced this pull request Oct 23, 2025
* adding availability zone to nnc spec

* adding optional kubebuilder annotation
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.

4 participants