Skip to content
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

Bump github.com/operator-framework/operator-sdk from 0.13.0 to 1.27.0 #112

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Feb 3, 2023

Bumps github.com/operator-framework/operator-sdk from 0.13.0 to 1.27.0.

Release notes

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

v1.27.0

Changes

  • operator-sdk run bundle(-upgrade): Change default of the --security-context-config flag to be legacy instead of restricted. (#6210)
  • operator-sdk run bundle: When creating the CatalogSource, we now set the grpcPodConfig.SecurityContextConfig to the value of the --security-context-config flag. (#6210)
  • The scorecard-test-kuttl image always prints the kuttl logs in case there is an error processing the kuttl report. (#6225)

Bug Fixes

  • operator-sdk bundle validate: Fix a bug in the Kubernetes 1.25 validation logic that would warn that a Kubernetes resource was deprecated without checking the group that contains the resource. (i.e if apps/deployments was deprecated and you used other/deployments you would recieve a warning)". The validation logic will now verify the group and resource before issuing a warning. (#6227)
  • operator-sdk run bundle(-upgrade): Fix a bug where SQLite bundle images were failing to be run properly due to a change in the default channel that is used by run bundle(-upgrade) when creating a subscription. (#6210)
  • operator-sdk run bundle(-upgrade): Update the logic used to set a Registry Pod's PSA configuration to fix a bug where a Pod's containers still had a restrictive SecurityContext even when setting --security-context-config=legacy. (#6210)
  • For operator-sdk bundle validate: Fix a bug that would make the command exit with a 0 exit code even if there were validation failures. (#6274)
  • (scorecard): Fixes a bug where an error would be thrown if a Custom Resource did not have a .spec field, which is a perfectly valid scenario. Instead of throwing an error scorecard will now issue a suggestion. (#6245)

v1.26.0

Additions

  • For operator-sdk bundle validate: When checking for Kubernetes APIs deprecated in Kubernetes v1.25.0 the ClusterServiceVersion's CustomResourceDefinitions, ClusterPermissions, and Permissions are now validated to ensure no references to deprecated APIs are being made. (#6119)

Changes

  • (images): Bumps all Operator SDK maintained images to now use ubi(-minimal) tag 8.7. (#6175)

Bug Fixes

  • ansible: fixed "make run" so it finds local roles. (#6110)
  • For operator-sdk run bundle(-upgrade): fix a bug in the logic that would attempt to create a ConfigMap that contained the entire contents of an FBC. Now if the FBC contents are to large to fit into a single ConfigMap, the FBC contents will be partitioned and split amongst multiple ConfigMap resources. (#6182)

v1.25.4

Changes

  • operator-sdk run bundle(-upgrade): Change default of the --security-context-config flag to be legacy instead of restricted. (#6261)
  • operator-sdk run bundle: When creating the CatalogSource, we now set the grpcPodConfig.SecurityContextConfig to the value of the --security-context-config flag. (#6261)

Bug Fixes

  • operator-sdk bundle validate: Fix a bug in the Kubernetes 1.25 validation logic that would warn that a Kubernetes resource was deprecated without checking the group that contains the resource. (i.e if apps/deployments was deprecated and you used other/deployments you would recieve a warning)". The validation logic will now verify the group and resource before issuing a warning. (#6263)
  • For operator-sdk run bundle(-upgrade): fix a bug in the logic that would attempt to create a ConfigMap that contained the entire contents of an FBC. Now if the FBC contents are to large to fit into a single ConfigMap, the FBC contents will be partitioned and split amongst multiple ConfigMap resources. (#6262)
  • operator-sdk run bundle(-upgrade): Fix a bug where SQLite bundle images were failing to be run properly due to a change in the default channel that is used by run bundle(-upgrade) when creating a subscription. (#6261)
  • operator-sdk run bundle(-upgrade): Update the logic used to set a Registry Pod's PSA configuration to fix a bug where a Pod's containers still had a restrictive SecurityContext even when setting --security-context-config=legacy. (#6261)
  • (scorecard): Fixes a bug where an error would be thrown if a Custom Resource did not have a .spec field, which is a perfectly valid scenario. Instead of throwing an error scorecard will now issue a suggestion. (#6266)

v1.25.3

Bug Fixes

... (truncated)

Commits

Dependabot compatibility score

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)

Bumps [github.com/operator-framework/operator-sdk](https://github.com/operator-framework/operator-sdk) from 0.13.0 to 1.27.0.
- [Release notes](https://github.com/operator-framework/operator-sdk/releases)
- [Changelog](https://github.com/operator-framework/operator-sdk/blob/master/.goreleaser.yml)
- [Commits](operator-framework/operator-sdk@v0.13.0...v1.27.0)

---
updated-dependencies:
- dependency-name: github.com/operator-framework/operator-sdk
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants