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.26.0 #26

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.26.0.

Release notes

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

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.3

Bug Fixes

  • For the ansible operator container images, update them to properly pull in the base image that uses UBI 8.7. (#6206)

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)

... (truncated)

Commits
  • cbeec47 Release v1.26.0 (#6218)
  • 76df628 [master] image(ansible-operator): bump base to quay.io/operator-framework/ans...
  • 8043570 Add alerts to the sample Memcached operator (#6135)
  • e0f197c Add Operator Observability Best Practices (#5975)
  • 0d2fa86 Make refresh images github workflow push latest (#6208)
  • a1b976e Add best practice for designing lean operator (#6164)
  • 85dda78 Updated the content to coherent with the code snippet (#6199)
  • f2ac68f update docs for operator-sdk run bundle with SQLite (#6054)
  • df45989 move everettraven from reviewer to approver (#6192)
  • dd20be4 (bugfix): update run bundle(-upgrade) logic (#6182)
  • 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 #29.