Bump github.com/vmware-labs/reconciler-runtime from 0.13.0 to 0.14.0 by dependabot[bot] · Pull Request #319 · servicebinding/runtime
Bumps github.com/vmware-labs/reconciler-runtime from 0.13.0 to 0.14.0.
Release notes
Sourced from github.com/vmware-labs/reconciler-runtime's releases.
v0.14.0
Breaking changes
- Kubernetes 1.28 types and client-go are in use. Any upstream breaking changes are reflected here.
- status
InitiazeConditions()is deprecated in favor ofInitializeConditions(context.Context). Support may be removed in a future release, users are encuraged to migrate.ConditionSet#Manageis deprecated in favor ofConditionSet#ManageWithContext. Support may be removed in a future release, users are encuraged to migrate.Highlights
Duck typed resources may now be used directly with the client and reconciled. These are structured types that represent a subset of many arbitrary resources. The APIVersion and Kind fields must be set explicitly on the object and the type must not be registered with the scheme. See Reconcilers in the readme for a discussion of the different types of resources that can be used and the tradeoff for each type.
Pinned reconcile time. Testing reconciler that write the current time back to the resource can be difficult to test because the result is ephemeral by nature. Each reconcile request now captures the current time at the start of the request and makes that value available to nested reconcilers for use instead of
time.Now. This value can also be defined in individual test cases so that the reconciler output is deterministic. See Time in the readme for an overview of the new APIs.What's Changed
- Duck type clients and reconcilers by
@scothisin vmware-labs/reconciler-runtime#402- Bump gomodules.xyz/jsonpatch/v2 from 2.3.0 to 2.4.0 by
@dependabotin vmware-labs/reconciler-runtime#403- Kubernetes 1.28 support by
@scothisin vmware-labs/reconciler-runtime#404Full Changelog: vmware-labs/reconciler-runtime@v0.13.0...v0.14.0
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot will merge this PR once CI passes on it, as requested by @scothis.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)