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

feat: use new property name for node count property + specify the core properties (node count, total/allocatable/available CPU/memory) #810

Merged

Conversation

michaelawyu
Copy link
Contributor

Description of your changes

This PR updates AKS property provider and related materials to use the new property name for the node count property (kubernetes.azure.com/node-count -> kubernetes-fleet.io/node-count),

I have:

  • Run make reviewable to ensure this PR is ready for review.

How has this code been tested

  • Unit tests
  • Integration tests
  • E2E tests

Special notes for your reviewer

Important: changes in this PR should only be rolled out after the RP E2E tests are updated and rolled out.

apis/cluster/v1/commons.go Outdated Show resolved Hide resolved
pkg/propertyprovider/aks/provider.go Outdated Show resolved Hide resolved
@michaelawyu michaelawyu changed the title feat: use new property name for node count property feat: use new property name for node count property + specify the core properties (node count, total/allocatable/available CPU/memory) May 13, 2024
@@ -136,6 +137,7 @@ var _ = Describe("Test Internal Member Cluster Controller", Serial, func() {
Expect(updatedHealthCond.Reason).To(Equal(EventReasonInternalMemberClusterHealthy))

By("checking updated member cluster usage")
Expect(imc.Status.Properties[propertyprovider.NodeCountProperty].Value).ShouldNot(BeEmpty())
Copy link
Contributor

Choose a reason for hiding this comment

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

do we know how many nodes does this cluster have?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

With the dummy env I am not sure, but there will be a PR that re-factors the tests for this controller and we will using the full comparison like the one in the E2E tests for this part.

pkg/propertyprovider/aks/provider.go Show resolved Hide resolved
@ryanzhang-oss ryanzhang-oss merged commit e3ff5b9 into Azure:main May 14, 2024
12 checks passed
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