chore(deps): update service-catalog to v0.10.0 - #361
Merged
Merged
Conversation
JoseSzycho
approved these changes
Sep 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Update compute to
go.miloapis.com/service-catalog v0.10.0, which contains the consumer-provider fix from milo-os/service-catalog#107.That release removes the per-
ServiceConsumerfive-minuteRequeueAfter. Compute currently averages about 1.8consumer-serviceconsumerreconciles/sec because the old provider schedules one full active-set scan per watched consumer. This update makes the provider event-driven and removes that aggregate resync churn.Part of #355.
Validation
go test ./internal/controller -run 'TestMergeDeploymentMetadata' -count=1go test $(go list ./... | grep -v '/internal/controller$')The full local suite is otherwise green but the envtest-backed controller suite cannot start because the repository's Darwin
etcdbinary is not present atbin/k8s/1.31.0-darwin-arm64/etcd; CI provides that prerequisite.