Bump github.com/operator-framework/operator-sdk from 1.29.0 to 1.30.0

[dependabot]

Bumps github.com/operator-framework/operator-sdk from 1.29.0 to 1.30.0.

Release notes

Sourced from github.com/operator-framework/operator-sdk's releases.

v1.30.0

Additions

• Add a Parameter to the Makefile to allow modifying the 'operator-sdk' binary before running any commands. If necessary, a specific version of the SDK can be downloaded for cases when the project has yet to upgrade to a later or latest version. (#6443)
• Currently, the operator SDK for the Ansible operator lacks options to customize the leader election resource lock behavior. This limits the flexibility of the operator and prevents users from adjusting lease duration and renew deadline according to their specific needs. Changes: Implemented enhancements to the operator SDK to include additional flags for configuring leader election resource lock options. These changes provide users with the ability to specify the type of resource object used for locking during leader election and customize the lease duration and renew deadline. Introduced --leader-elect-lease-duration flag to allow users to define the duration that non-leader candidates will wait to force acquire leadership. The default duration is set to 15 seconds. Introduced --leader-elect-renew-deadline flag, enabling users to set the renew deadline, which determines the duration that the acting control plane will retry refreshing leadership before giving up. The default duration is set to 10 seconds. Introduced --leader-elect-resource-lock flag to allow users to define the type of resource object that is used for locking during leader election. Supported options are 'leases', 'endpointsleases', and 'configmapsleases'. The default option is 'leases'. These changes provide more flexibility and control over leader election behavior, allowing operators to adapt to various deployment scenarios and specific requirements. (#6426)

Changes

• Currently, when setting overrideValues in your watches.yaml, every entry is logged with its key and its value. When working with confidential information such as credentials, logging those information would not be optimal nor desirable. Therefore, there should be a way to silence/suppress these values. This feature introduces the --suppress-override-values boolean-flag for the helm-operator. When set to true, the value of the overrideValues entry is sanitized with this value "****". This is a simple example of overrideValues of the watches.yaml ```yaml overrideValues: x: y

The default-value of `--suppress-override-values` is `false` so therefore we would get this warning logged: `Chart value x overridden to y by operator's watches.yaml`
When setting `--suppress-override-values` `true` the warning will be logged in the following manner: `Chart value x overridden to **** by operator's watches.yaml`. ([#6469](https://github.com/operator-framework/operator-sdk/pull/6469))
- (images): Bumps all Operator SDK maintained images to now use ubi(-minimal) tag 8.8. ([#6466](https://github.com/operator-framework/operator-sdk/pull/6466))
Bug Fixes

In run bundle-upgrade, hash the cache directory name to avoid error of too long file name. (#6477)

Commits

• b794fe9 Release v1.30.0 (#6479)
• 93a2a32 [master] image(ansible-operator): bump base to quay.io/operator-framework/ans...
• a99d7ed Fix bug: run bundle-upgrade with long image names (#6477)
• 50c6ac0 (fix): (ansible): temporarily ignore CVEs (#6471)
• f8f9819 feat: allow operator-sdk install to be customizable (#6443)
• 716bfab fix: update test-docs to fail less randomly (#6464)
• deb20c6 (chore): bump dependencies to resolve CVE issues (#6383)
• 2f54287 Add Leader Election Resource Lock Options (#6426)
• b7a4292 website: docs: add oxford comma + simplify example (#6452)
• feeea7e fix function name in comments (#6459)
• Additional commits viewable in compare view

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 commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dfarrell07]

E2E (1.24) failed, re-running.