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

Move VNet Reconciliation to the Cluster Actuator #22

Merged
merged 6 commits into from
Oct 29, 2018

Conversation

marwanad
Copy link
Member

This moves handling of VNets from the machine actuator to the cluster actuator.

Machines in the same cluster are all connected to the same virtual network and each has its own NIC.

Closes #9

Copy link
Contributor

@vannrt vannrt left a comment

Choose a reason for hiding this comment

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

Looks good to me overall. You need to update the unit test names however. The Makefile only considers tests with the pattern Test(\w)*Unit to be unit tests.

I believe the previous PR also had the same issue (though I didn't catch them that time). I'll take this up. I'll take the unit test issue regarding the previous PR.

@@ -79,6 +81,16 @@ func (azure *AzureClusterClient) Reconcile(cluster *clusterv1.Cluster) error {
if err != nil {
return fmt.Errorf("error waiting for network security group creation or update: %v", err)
}

// Reconcile virutal network
Copy link
Contributor

Choose a reason for hiding this comment

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

nit virutal -> virtual

vannrt
vannrt previously approved these changes Oct 29, 2018
@vannrt vannrt merged commit 35cdb81 into kubernetes-sigs:master Oct 29, 2018
karthikbalasub pushed a commit to karthikbalasub/cluster-api-provider-azure-1 that referenced this pull request Dec 16, 2022
…ig_validation

fix kubeletconfig validation
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.

2 participants