fix(deps): update non-minor dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
github.com/sap/component-operator-runtime	v0.3.34 -> v0.3.58					require	patch
go (source)	1.23.0 -> 1.23.4					golang	patch
sigs.k8s.io/controller-runtime	v0.19.0 -> v0.19.3					require	patch

---

Release Notes

sap/component-operator-runtime (github.com/sap/component-operator-runtime)

v0.3.58

Compare Source

This release is a bugfix release for the clm cli. So far, while applying or deleting a release, clm was aborting immediately if an error occurred. This is not very convenient. At least in some ephemeral error situations, it should behave in a more resilient way. So, with this release, clm tries to recognise such ephemeral errors (for example 409 - Conflict responses from the API server), and retries the failing operation a couple of times.

v0.3.57

Compare Source

v0.3.56

Compare Source

Enhancements

A new flag --create-namespace was added to clm apply. If specified the specified release namespace will be auto-created if missing. Note that in that case, the namespace is not part of the release inventory. In particular, it will not be deleted if the component gets deleted.

v0.3.55

Compare Source

This release adds a new interface PolicyConfiguration that component types (or their spec types) can implement:

type PolicyConfiguration interface {
  // Get adoption policy.
  // Must return a valid AdoptionPolicy, or the empty string (then the reconciler/framework default applies).
  GetAdoptionPolicy() reconciler.AdoptionPolicy
  // Get update policy.
  // Must return a valid UpdatePolicy, or the empty string (then the reconciler/framework default applies).
  GetUpdatePolicy() reconciler.UpdatePolicy
  // Get delete policy.
  // Must return a valid DeletePolicy, or the empty string (then the reconciler/framework default applies).
  GetDeletePolicy() reconciler.DeletePolicy
}

Through this interface, components can override the framework default policies that would otherwise apply. Of course, dependent resources can still override the behaviour using the well-known annotations. For easier consumption (similar to the already existing Configuration interfaces), there is a standard implementation PolicySpec that components may embed into their spec).

Furthermore, the semantics of the deletion policy was slightly changed:

1. Other than before, the deletion policy is now ignored during apply. That is, if an existing object becomes obsolete while applying a new revision of the depdendents' manifests, it will be always deleted now, even if it has an effective deletion policy 'orphan'. In other words, the deletion policy will only be honoured if the owning component itself is deleted.
2. So far, a component's deletion will block if it contains extension types, and there exist any foreign instances of these types in the cluster; this check will now be skipped if all dependents of the component have an effective deletion policy 'orphan'.

v0.3.54

Compare Source

This release adds some new template functions to HelmGenerator and KustomizeGenerator.

1. Template functions for bitwise operations:

   • func bitwiseShiftLeft(by any, arg any) (uint64, error)
   • func bitwiseShiftRight(by any, arg any) (uint64, error)
   • func bitwiseAnd(args ...any) (uint64, error)
   • func bitwiseOr(args ...any) (uint64, error)
   • func bitwiseXor(args ...any) (uint64, error)

2. Functions for IPv4 address handling:

   • func parseIPv4Address(data any) (uint32, error)
   • func formatIPv4Address(data any) (string, error)

v0.3.53

Compare Source

v0.3.52

Compare Source

This is a bugfix release, but it slightly changes the procedure how dependent objects are reconciled. In detail:

Until now, reconciler.Apply() (which is what happens if a component is reconciled, not deleted) first deleted all redundant objects, that is objects which appear in the component's inventory, but are no longer part of the current manifest list. Only after all redundant objects were gone, the reconciliation of the current dependents was started. This potentially caused some deadlock situations, e.g. in component-operator. To overcome, the deletion part was shifted to the end of
reconciler.Apply(), after the application of the current manifest list. This should not be a noticeable change. However, the completion handling still happens early (before the reconciliation of the dependents), and was slightly changed as well; for example, object deletions happening as consequence of a completion now no longer honour delete-order or delete-policy.

v0.3.51

Compare Source

v0.3.50

Compare Source

v0.3.49

Compare Source

v0.3.48

Compare Source

v0.3.47

Compare Source

v0.3.46

Compare Source

v0.3.45

Compare Source

This is a bug fixing release. Fixes:

• Issue #​160
• some smaller issues with the clm cli

v0.3.44

Compare Source

v0.3.43

Compare Source

This release add a new command line utility clm. It can be used (similar to helm) to deploy arbitrary components to a kubernetes cluster, without requiring any additional operators or other resources to be installed in the cluster:

A Kubernetes package manager

Common actions for clm:
- clm apply              Apply given component manifests to Kubernetes cluster
- clm delete             Remove component from Kubernetes cluster
- clm status             Show component status
- clm ls                 List components

Usage:
  clm [command]

Available Commands:
  apply       Apply component
  completion  Generate the autocompletion script for the specified shell
  delete      Delete component
  help        Help about any command
  list        List components
  status      Show component status
  version     Show version

Flags:
      --as string                      Username to impersonate for the operation. User could be a regular user or a service account in a namespace.
      --as-group stringArray           Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
      --as-uid string                  UID to impersonate for the operation.
      --cache-dir string               Default cache directory (default "/Users/xxx/.kube/cache")
      --certificate-authority string   Path to a cert file for the certificate authority
      --client-certificate string      Path to a client certificate file for TLS
      --client-key string              Path to a client key file for TLS
      --cluster string                 The name of the kubeconfig cluster to use
      --context string                 The name of the kubeconfig context to use
      --disable-compression            If true, opt-out of response compression for all requests to the server
      --insecure-skip-tls-verify       If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
      --kubeconfig string              Path to the kubeconfig file to use for CLI requests.
  -n, --namespace string               If present, the namespace scope for this CLI request (default "default")
      --request-timeout string         The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0")
  -s, --server string                  The address and port of the Kubernetes API server
      --tls-server-name string         Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used
      --token string                   Bearer token for authentication to the API server
      --user string                    The name of the kubeconfig user to use
  -h, --help                           help for clm

Use "clm [command] --help" for more information about a command.

For example:

clm  -n my-ns apply my-comp ./my-manifests -f my-values.yaml

A kubeconfig can be provided by flag --kubeconfig. If not set, the environment variable KUBECONFIG will be used to get the path to the kubeconfig. The provided manifests can either be a helm chart (detected by the presence of a Chart.yaml file in the specified directory), or a kustomization folder (otherwise). In the kustomization case (no Chart.yaml), if there is no kustomization.y(a)ml file found, then the directory will be searched recursively for all files ending with .y(a)ml, and the content of all these files will form the set of manifests to be deployed.

Under the hood, component-operator-runtime is used to render and deploy the manifests. That means, all the features described in the documentation are available, such as:

• apply/delete waves
• smart handling of custom types (such as CRDs)
• improved status detection
• go templating also for kustomizations resp. plain yaml sources

v0.3.42

Compare Source

v0.3.41

Compare Source

v0.3.40

Compare Source

v0.3.39

Compare Source

v0.3.38

Compare Source

v0.3.37

Compare Source

v0.3.36

Compare Source

v0.3.35

Compare Source

golang/go (go)

v1.23.4

v1.23.3

v1.23.2

v1.23.1

kubernetes-sigs/controller-runtime (sigs.k8s.io/controller-runtime)

v0.19.3

Compare Source

What's Changed

• 🐛 Refactor certificate watcher to use polling, instead of fsnotify by @​k8s-infra-cherrypick-robot in https://github.com/kubernetes-sigs/controller-runtime/pull/3023
• 🐛 Use leader elector with client timeout by @​k8s-infra-cherrypick-robot in https://github.com/kubernetes-sigs/controller-runtime/pull/3031

Full Changelog: kubernetes-sigs/controller-runtime@v0.19.2...v0.19.3

v0.19.2

Compare Source

What's Changed

• ✨ Add EnableWatchBookmarks option to cache informers by @​k8s-infra-cherrypick-robot in https://github.com/kubernetes-sigs/controller-runtime/pull/3018

Full Changelog: kubernetes-sigs/controller-runtime@v0.19.1...v0.19.2

v0.19.1

Compare Source

What's Changed

• [release-0.19] 🌱 Verify PR titles with shell script by @​k8s-infra-cherrypick-robot in https://github.com/kubernetes-sigs/controller-runtime/pull/2947
• [release-0.19] 🐛 Fakeclient: preserve TypeMeta for PartialObjectMeta resources by @​k8s-infra-cherrypick-robot in https://github.com/kubernetes-sigs/controller-runtime/pull/2951
• [release-0.19] 🌱 pr-verify: use env var for passing the PR title by @​k8s-infra-cherrypick-robot in https://github.com/kubernetes-sigs/controller-runtime/pull/2962
• [release-0.19] 🌱 pr-verify: use env var for passing the PR title by @​k8s-infra-cherrypick-robot in https://github.com/kubernetes-sigs/controller-runtime/pull/2965
• [release-0.19] 🌱 Fix PR verify action by @​k8s-infra-cherrypick-robot in https://github.com/kubernetes-sigs/controller-runtime/pull/2974
• [release-0.19] 🐛 Fakeclient: Fix TOCTOU races by @​k8s-infra-cherrypick-robot in https://github.com/kubernetes-sigs/controller-runtime/pull/2992

Full Changelog: kubernetes-sigs/controller-runtime@v0.19.0...v0.19.1

---

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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 9 additional dependencies were updated

Details:

Package	Change
github.com/Masterminds/semver/v3	v3.2.1 -> v3.3.0
github.com/Masterminds/sprig/v3	v3.2.3 -> v3.3.0
github.com/huandu/xstrings	v1.4.0 -> v1.5.0
github.com/prometheus/client_golang	v1.19.1 -> v1.20.5
github.com/sap/go-generics	v0.2.13 -> v0.2.21
github.com/shopspring/decimal	v1.3.1 -> v1.4.0
github.com/spf13/cast	v1.6.0 -> v1.7.0
golang.org/x/time	v0.7.0 -> v0.8.0
sigs.k8s.io/structured-merge-diff/v4	v4.4.2 -> v4.5.0