fix: Add SubnetGUID to MT PodNetwork CRD (#2321)

* Update SubnetResourceId to SubnetGUID

* Leave subnetResourceID as is, just add subnetGUID field to PN CRD

* Update order of properties in PodNetworkSpec

---------

Co-authored-by: Samarth Shah <[email protected]>

Author: samarths-msft

crd/multitenancy/api/v1alpha1/podnetwork.go

@@ -18,6 +18,7 @@ import (
 // +kubebuilder:printcolumn:name="Address Prefixes",type=string,priority=1,JSONPath=`.status.addressPrefixes`
 // +kubebuilder:printcolumn:name="Network",type=string,priority=1,JSONPath=`.spec.vnetGUID`
 // +kubebuilder:printcolumn:name="Subnet",type=string,priority=1,JSONPath=`.spec.subnetResourceID`
+// +kubebuilder:printcolumn:name="SubnetGUID",type=string,priority=1,JSONPath=`.spec.subnetGUID`
 type PodNetwork struct {
 	metav1.TypeMeta   `json:",inline"`
 	metav1.ObjectMeta `json:"metadata,omitempty"`
@@ -42,6 +43,8 @@ type PodNetworkSpec struct {
 	VnetGUID string `json:"vnetGUID,omitempty"`
 	// customer subnet id
 	SubnetResourceID string `json:"subnetResourceID,omitempty"`
+	// customer subnet guid
+	SubnetGUID string `json:"subnetGUID,omitempty"`
 }
 
 // Status indicates the status of PN

crd/multitenancy/manifests/multitenancy.acn.azure.com_podnetworks.yaml

@@ -33,6 +33,10 @@ spec:
       name: Subnet
       priority: 1
       type: string
+    - jsonPath: .spec.subnetGUID
+      name: SubnetGUID
+      priority: 1
+      type: string
     name: v1alpha1
     schema:
       openAPIV3Schema:
@@ -53,6 +57,9 @@ spec:
           spec:
             description: PodNetworkSpec defines the desired state of PodNetwork
             properties:
+              subnetGUID:
+                description: customer subnet guid
+                type: string
               subnetResourceID:
                 description: customer subnet id
                 type: string