generated from SAP/repository-template
-
Notifications
You must be signed in to change notification settings - Fork 1
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
fix(deps): update non-minor dependencies #120
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/non-minor-deps
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
186dd9d
to
dc03c75
Compare
dc03c75
to
320c15c
Compare
320c15c
to
b70dfeb
Compare
b70dfeb
to
dda5d2e
Compare
dda5d2e
to
ea042be
Compare
ea042be
to
31e1709
Compare
31e1709
to
9d8e319
Compare
9d8e319
to
baa9dea
Compare
baa9dea
to
d6320ce
Compare
b6b3522
to
cc5686d
Compare
cc5686d
to
fecbc1e
Compare
fecbc1e
to
da5b1bd
Compare
da5b1bd
to
a3e3f1a
Compare
a3e3f1a
to
2cb1b38
Compare
2cb1b38
to
35437be
Compare
35437be
to
ac0e16b
Compare
ac0e16b
to
7577b05
Compare
7577b05
to
9037e7d
Compare
9037e7d
to
a0588d3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
v0.3.67
->v0.3.80
1.24.0
->1.24.1
v0.32.1
->v0.32.2
v0.32.1
->v0.32.2
v0.32.1
->v0.32.2
v0.32.1
->v0.32.2
v0.32.1
->v0.32.2
v0.20.1
->v0.20.3
1a91ccc
->f80bc5d
Release Notes
sap/component-operator-runtime (github.com/sap/component-operator-runtime)
v0.3.80
Compare Source
v0.3.79
Compare Source
Enhancements
So far, the framework emitted really many component events, mostly if the component is in
Processing
state. That often exceeded the burst of the event broadcaster provided by controller-runtime (b=25, r=1/300
, see https://github.com/kubernetes/client-go/blob/b46275ad754db4dd7695a48cd3ca673e0154dd9e/tools/record/events_cache.go#L43).We change that now. If there are identical subsequent events produced for a component, only the first one will be emitted within 5 minutes; after 5 minutes, again one instance of the throttled event may be sent, and so on.
v0.3.78
Compare Source
Notable changes
status.ProcessingDigest
) is now considering themetadata.generation
of the component.v0.3.77
Compare Source
Enhancements
New methods are added to
cluster.Client
:In addition there is a new reconciler option
with
This allow to replace or modify the default component/hook client that would be used by the reconciler
v0.3.76
Compare Source
v0.3.75
Compare Source
Enhancements
Additional managed types
By its nature, component-operator-runtime tries to handle extension types (such as CRDs or API groups added through APIService federation), and instances of these types, in a smart way.
That is, if the component contains extension types, and also instances of these types, it tries to process things in the right order; that means, during apply the instances will be applied as late as possible (to ensure that controllers and webhooks are up); and during delete, the instances will be deleted as early as possible (to ensure that controllers and webhooks are still there). Furthermore, during deletion, foreign instances (that is, instances of these types that are not part of the component) block the deletion of the whole component.
Sometimes, components are implicitly adding extension types to the cluster; in the sense that the extension types are not explicitly part of the manifests, but added in the dark through controllers, once running. A typical example are crossplane providers.
This PR tries to add some relief in this situation. Components can now list 'additional managed types', by implementing the
TypeConfiguration
interface; these 'additional managed types' will be treated in the same way as extension types which are explicitly mentioned in the manifest.Improved APIService handling
Up to now,
APIService
objects were deployed along with the other regular (that was: unmanaged) objects of the current apply wave. As a consequence, if the federated API server was not yet ready,stale group version
errors were returned by the discovery API of the main API server. To overcome this problem,APIService
objects receive a special handling now, in the sense that they are reconciled (in the apply wave) after all other regular objects, and before all managed instances. That means: within each apply order, objects are deployed to readiness in three sub stagesAPIService
objects)APIService
)Within each of these sub groups, the static ordering defined in
sortObjectsForApply()
is effective.More robust handling of external recreations happening during deletion
Previously there was a rare race condition while deleting objects (either during component delete or component apply):
The old logic was:
ScheduledForDeletion
during apply or if the whole component is being deleted); if successful (that is API server responds with 2xx) then the inventory status of the dependent object is set toDeleting
.Now, if the object was recreated by someone right between 1. and 2. then the reconciler went stuck.
Note that really does not happen usually (also because the critical period is very, very short).
To overcome, we are now checking the deletion timestamp of the dependent object (if still or again existing). If it has none, then we check the owner; if it is not us, then we give the object up (because apparently, someone else has just recreated it).
v0.3.74
Compare Source
Improvements
So far, there was no special logic to check status status of
CustomResourceDefinition
andAPIService
resources.That is, they were considered ready immediately, which was causing problems (for example, lookup errors when querying the discovery API immediately after creating an
APIService
, such as... stale GroupVersion discovery ...
).To mitigate, the default status analyzer now evaluates existing conditions (such as the
Available
condition ofAPIService
).v0.3.73
Compare Source
v0.3.72
Compare Source
Incompatible changes
Background: values passed to the built-in generators and transformers
are of type
map[string]any
. Of course, templates are rendered with themissingkey=zero
option.But still, if a key is missing in the values, the empty value of
any
(returned in this case)makes the go templating engine return
<no value>
in that case.Helm decided to override that by replacing all occurrences of the string
<no value>
in any template output.Starting with this PR we adopt the helm approach, and do the same.
v0.3.71
Compare Source
Incompatible changes
Orphan
is slightly changed; previouslyOrphan
had no effect if a dependent object became redundant during apply (that is, it was part of the component manifest before, and is no longer now). Now, if an object has an effective deletion policyOrphan
, then it will be always orphaned ifEnhancements
OrphanOnApply
andOrphanOnDelete
, with the obvious meaning.apiResources
is added forKustomizeGenerator
. It returns[]*metav1.APIResourceList
, as returned by the discovery client's methodServerGroupsAndResources
, see https://pkg.go.dev/k8s.io/[email protected]/discovery#ServerResourcesInterface.ServerGroupsAndResources.v0.3.70
Compare Source
Changes
This release finalizes the reworking of the force-reapply logic started in https://github.com/SAP/component-operator-runtime/releases/tag/v0.3.62.
So far, a dependent object was applied to the cluster if
status.inventory[].lastAppliedAt
timestamp is set and is more than 60m in the past.The third condition is now changed to
status.inventory[].lastAppliedAt
timestamp is not set, or is set and is more than 60m in the past.As a consequence, the component CRD now must contain the
status.inventory[].lastAppliedAt
field, that is the consumers must have regenerated their CRD to reflect the current component-operator-runtime API types, as already stated in the release notes of v0.3.62.v0.3.69
Compare Source
Enhancements
Starting with this release, the deletion of dependent objects will fail unless the existing value of the owner-id label of the dependent object matches the component that wants to delete it. If the owner-id label is missing, or the value does not match, the deletion will be rejected.
v0.3.68
Compare Source
kubernetes/apiextensions-apiserver (k8s.io/apiextensions-apiserver)
v0.32.2
Compare Source
kubernetes/apimachinery (k8s.io/apimachinery)
v0.32.2
Compare Source
kubernetes/client-go (k8s.io/client-go)
v0.32.2
Compare Source
kubernetes/code-generator (k8s.io/code-generator)
v0.32.2
Compare Source
kubernetes/kube-aggregator (k8s.io/kube-aggregator)
v0.32.2
Compare Source
kubernetes-sigs/controller-runtime (sigs.k8s.io/controller-runtime)
v0.20.3
Compare Source
What's Changed
Full Changelog: kubernetes-sigs/controller-runtime@v0.20.2...v0.20.3
v0.20.2
Compare Source
What's Changed
Full Changelog: kubernetes-sigs/controller-runtime@v0.20.1...v0.20.2
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.