bigkevmcd / tekton-polling-operator

A simple git repository poller.
Apache License 2.0
26 stars 12 forks source link

Bump github.com/operator-framework/operator-sdk from 0.19.4 to 1.25.2 #24

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps github.com/operator-framework/operator-sdk from 0.19.4 to 1.25.2.

Release notes

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

v1.25.2

Changes

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

v1.25.1

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. (#6123)

v1.25.0

Changes

  • (ansible/v1): Modified ansible scaffolding in order to incorporate changes with Kubebuilder on --component-config flag changes. Previously, the changes with --component-config flag were not considered by default. The following are the modifications: 1. If the --component-config flag is passed then look for - /manager in manager.yaml in order to add leader election id. If the component config flag is not passed then check for --leader-elect flag. 2. In manager_proxy_patch.yaml file, look for memory: 64Mi if the component flag is passed flag is passed. If not then look for --leader-elect. 3. Repeat the same logic for replacing the port number from the file. 4. At the end, update the manager.yaml file to avoid lint errors. (#6047)
  • (go/v3, hybrid.helm/v1-alpha, and quarkus/v1-alpha): Upgrade Kubernetes dependencies from 1.24 to 1.25. (#6044)
  • This PR bumped Kubebuilder to 3.7.1, with this version comes the addition of the --component-config flag. This flag is passed through operator-sdk init command. If this flag is passed through the command line as an argument then only the controller_manager_config.yaml file will be scaffolded in the manifest. If it is not passed then it will not scaffold out this file. The command for passing the flag is: operator-sdk init --domain example.com --repo github.com/example/memcached-operator --component-config. (#6047)
  • (ansible/v1): updates the base ansible base operator event api, api server, and proxy to now have a 5 second timeout when reading the request headers. This is to prevent the possibility of a Slowloris attack. (#6088)
  • Modified go version to 1.19 and Kubebuilder to 3.7.1. The config-gen is completely removed from Kubebuilder. As part of this bump, the website content of SDK was updated where the doc is referring to config-gen. (#6047)
  • Updated ginkgo to ginkgo/v2 in all of the files. (#6047)
  • Updated: - ginko to ginko/v2 - io/ioutil packages to either io or os since its not longer supported in go1.19. (#6047)
  • (helm/v1): Modified helm scaffolding in order to incorporate changes with Kubebuilder on --component-config flag changes. Previously, the changes with --component-config flag were not considered by default. The following are the modifications: 1. If the --component-config flag is passed then look for - /manager in manager.yaml in order to add leader election id. If the component config flag is not passed then check for --leader-elect flag. 2. In manager_proxy_patch.yaml file, look for memory: 64Mi if the component flag is passed flag is passed. If not then look for --leader-elect. 3. Repeat the same logic for replacing the port number from the file. 4. At the end, update the manager.yaml file to avoid lint errors. (#6047)
  • (ansible/v1, helm/v1): Added support to build multi-arch images from the project Makefile. A docker-buildx target will build the images for the platforms specified by the PLATFORMS variable. (#6093)

Bug Fixes

  • (docs) Update the go version in the developer guide. The documentation wasn't updated when the go version was bumped to v1.18. (#6101)
  • For operator-sdk run bundle and bundle-upgrade subcommands: Added --security-context-config flag to enable seccompprofile. It defaults to restricted to support k8s 1.25. You can disable it with --security-context-config=legacy. (#6062)

v1.24.1

Bug Fixes

  • For operator-sdk run bundle and bundle-upgrade subcommands: Added --security-context-config flag to enable seccompprofile. It defaults to restricted to support k8s 1.25. You can disable it with --security-context-config=legacy. (#6080)

v1.24.0

Changes

  • Bumping java-operator-plugins to v0.6.0. (#6007)

Bug Fixes

  • Support test selectors in scorecard-kuttl. This only works if you supply a test name in the config for the entrypoint in the scorecard test config.yaml In the stages.testssection add an entrypoint, in this entrypoint you add the name of the test you want to associate with the selector.

... (truncated)

Commits
  • b63b921 Release v1.25.2 (#6178)
  • 34ab17f [v1.25.x] (chore): bump ubi(-minimal) to 8.7 (#6177)
  • 162690f Update the keys and script one more time (#6163)
  • 51b7591 Fix secring. Signed with cncf key instead of mine. (#6161)
  • a30e6f0 Update gpg keys with new expiration date (#6152)
  • 81b0a5e add --mode 700 to gpg directory creation (#6147)
  • 8db8969 Release v1.25.1 (#6145)
  • d44ce84 bump operator-framework/api to commit b611f6cef49cb8c6d621145c4e31d8ddfd4c59f...
  • 3d4eb4b Release v1.25.0 (#6104)
  • 2bda9e1 [master] image(ansible-operator): bump base to quay.io/operator-framework/ans...
  • Additional commits viewable in compare view


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)
dependabot[bot] commented 1 year ago

Superseded by #25.