Skip to content

chore: backport changes from cncf/main (2025-12-10) #1243

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.

Sign up for GitHub

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

Closed
weng271190436 wants to merge 3 commits into from
Closed

chore: backport changes from cncf/main (2025-12-10) #1243

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3d594cc
fix: always sort bindings in the scheduler to ensure deterministic de…
michaelawyu Dec 10, 2025
0552f2e
feat: add status back-reporting support (1/, work applier side) (#327)
michaelawyu Dec 10, 2025
1ecee23
chore: backport changes from cncf/main, update module paths, and run …
Dec 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,9 @@ Azure Fleet repo contains the code that the [Azure Kubernetes Fleet Manager](htt
It follows the CNCF sandbox project [KubeFleet](https://github.com/kubefleet-dev/) and most of the development is done in the [KubeFleet](https://github.com/kubefleet-dev/).

## Get Involved
For any questions, please see the [KubeFleet discussion board](https://github.com/kubefleet-dev/kubefleet/discussions).
For any questions, please see the [KubeFleet discussion board](https://go.goms.io/fleet/discussions).

For any issues, please open an issue in the [KubeFleet](https://github.com/kubefleet-dev/kubefleet/issues)
For any issues, please open an issue in the [KubeFleet](https://go.goms.io/fleet/issues)


## Quickstart
Expand All @@ -27,7 +27,7 @@ To learn more about KubeFleet go to the [KubeFleet documentation](https://kubefl

You can reach the KubeFleet community and developers via the following channels:

* Q & A: [GitHub Discussions](https://github.com/kubefleet-dev/kubefleet/discussions)
* Q & A: [GitHub Discussions](https://go.goms.io/fleet/discussions)
* Slack: [The #KubeFleet Slack channel](https://cloud-native.slack.com/archives/C08KR7589R8)
* Mailing list: [mailing list](https://groups.google.com/g/kubefleet-dev)

Expand Down
2 changes: 1 addition & 1 deletion SUPPORT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ feature request as a new Issue.

For help and questions about using this project, please

* start the conversation in the [GitHub Discussions](https://github.com/kubefleet-dev/kubefleet/discussions/).
* start the conversation in the [GitHub Discussions](https://go.goms.io/fleet/discussions/).

We are actively exploring other means for developers, system admins, and anyone who has an interest
in the multi-cluster domain to engage with us. Please stay tuned.
8 changes: 4 additions & 4 deletions hack/Azure/property-based-scheduling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,7 @@ To set up Fleet using the clusters you just created, you will need to install Fl
First, clone the Fleet source code repository, which contains the Helm charts used for Fleet agent installation:

```sh
git clone https://github.com/kubefleet-dev/kubefleet.git
git clone https://go.goms.io/fleet.git
cd fleet
git checkout demo
```
Expand Down Expand Up @@ -405,7 +405,7 @@ spec:
EOF
```

The CRP API enables great flexibility; you can set up different requirements/preferences in combination, such as finding all clusters with at least 5 nodes and 10 available CPU cores, or 4 of all the clusters with the cheapest memory cost and the most amount of available memory. [Read Fleet's API definition to learn more](https://github.com/kubefleet-dev/kubefleet/blob/main/apis/placement/v1beta1/clusterresourceplacement_types.go).
The CRP API enables great flexibility; you can set up different requirements/preferences in combination, such as finding all clusters with at least 5 nodes and 10 available CPU cores, or 4 of all the clusters with the cheapest memory cost and the most amount of available memory. [Read Fleet's API definition to learn more](https://go.goms.io/fleet/blob/main/apis/placement/v1beta1/clusterresourceplacement_types.go).

## Clean things up

Expand All @@ -419,9 +419,9 @@ All the AKS clusters in the resource group will be removed.

## What's next

Congrats! We hope that property-based scheduling (preview) has improved your overall Fleet experience. If you have any questions, feedback, or concerns, please raise [a GitHub issue](https://github.com/kubefleet-dev/kubefleet/issues).
Congrats! We hope that property-based scheduling (preview) has improved your overall Fleet experience. If you have any questions, feedback, or concerns, please raise [a GitHub issue](https://go.goms.io/fleet/issues).

Aside from property-based scheduling, Fleet offers many other scheduling features that are useful in a
multi-cluster environment; check out the [How-to Guide: Using the Fleet `ClusterResourcePlacement` API](https://kubefleet.dev/docs/how-tos/crp/) for more information.

You can also review Fleet's [source code](https://github.com/kubefleet-dev/kubefleet/) or review its [documentation](https://kubefleet.dev/docs/) on GitHub.
You can also review Fleet's [source code](https://go.goms.io/fleet/) or review its [documentation](https://kubefleet.dev/docs/) on GitHub.
4 changes: 2 additions & 2 deletions pkg/controllers/workapplier/backoff_integration_test.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,7 +178,7 @@ var _ = Describe("exponential backoff", func() {
applyStrategy := &fleetv1beta1.ApplyStrategy{
WhenToTakeOver: fleetv1beta1.WhenToTakeOverTypeIfNoDiff,
}
createWorkObject(workName, memberReservedNSName2, applyStrategy, regularNSJSON)
createWorkObject(workName, memberReservedNSName2, applyStrategy, nil, regularNSJSON)
})

// For simplicity reasons, this test case will skip some of the regular apply op result verification
Expand Down Expand Up @@ -395,7 +395,7 @@ var _ = Describe("exponential backoff", func() {
WhenToTakeOver: fleetv1beta1.WhenToTakeOverTypeAlways,
WhenToApply: fleetv1beta1.WhenToApplyTypeAlways,
}
createWorkObject(workName, memberReservedNSName2, applyStrategy, regularNSJSON)
createWorkObject(workName, memberReservedNSName2, applyStrategy, nil, regularNSJSON)
})

// For simplicity reasons, this test case will skip some of the regular apply op result verification
Expand Down
3 changes: 3 additions & 0 deletions pkg/controllers/workapplier/controller.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -505,6 +505,9 @@ func (r *Reconciler) Reconcile(ctx context.Context, req ctrl.Request) (ctrl.Resu
trackWorkAndManifestProcessingRequestMetrics(work)

// Requeue the Work object with a delay based on the requeue rate limiter.
//
// Note (chenyu1): at this moment the work applier does not register changes on back-reported
// status as a trigger for resetting the rate limiter.
requeueDelay := r.requeueRateLimiter.When(work, bundles)
klog.V(2).InfoS("Requeue the Work object for re-processing", "work", workRef, "delaySeconds", requeueDelay.Seconds())
return ctrl.Result{RequeueAfter: requeueDelay}, nil
Expand Down
Loading
Loading