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

dependabot(deps): bump github.com/Azure/azure-service-operator/v2 from 2.9.0 to 2.11.0 #5279

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

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 18, 2024

Bumps github.com/Azure/azure-service-operator/v2 from 2.9.0 to 2.11.0.

Release notes

Sourced from github.com/Azure/azure-service-operator/v2's releases.

v2.11.0

Release notes

Breaking changes

Moved all the "ARM" variants of the CRD types into dedicated subpackages

This is only breaking for consumers of the Go package, not for users of the YAML, and only for those using the ARM types directly.

Upcoming Breaking changes

Deprecated managedclusters.containerservice.azure.com API versions

  • The v1api20210501 and v1api20231102preview versions will be removed in ASO release 2.12.
  • The v1api20230201 version will be removed in ASO release 2.13.

We recommend you move to use a different CRD version to avoid errors.

For more details see the breaking changes document.

New resources

  • Add support for new insights DiagnosticSettings resource (#4363)
  • Add support for new alertsmanagement SmartDetectorAlertRule resource (#4375)
  • Add support for new containerservice API version 2024-09-01 (#4419)
  • Add support for new network API version 2024-03-01. This includes VNet, Subnet, and many other networking resources (#4431)
  • And support for new network PrivateDNS API version 2024-06-01 (#4431)

Features

  • Add support for dynamic secret or configmap export. See our documentation on Expressions (#4362, #4398)

Improvements

  • Updated numerous dependencies

Bug fixes

  • asoctl: Handle deprecated trustedaccessrolebinding storage version in asoctl clean crds (#4403)

Documentation

  • Clarify some PostgreSQL User documentation (#4360)
  • Improved CRD documentation by moving the "ARM" variants of the CRD types into dedicated subpackages.
  • Capture recent advice to users in our docs (#4396)

Full Changelog: Azure/azure-service-operator@v2.10.0...v2.11.0

v2.10.0

Release notes

... (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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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 dependabot bot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. labels Nov 18, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign fabriziopandini for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Nov 18, 2024
@k8s-ci-robot
Copy link
Contributor

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Nov 18, 2024
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/Azure/azure-service-operator/v2-2.11.0 branch from 899a65a to bb5a496 Compare November 18, 2024 23:30
Bumps [github.com/Azure/azure-service-operator/v2](https://github.com/Azure/azure-service-operator) from 2.9.0 to 2.11.0.
- [Release notes](https://github.com/Azure/azure-service-operator/releases)
- [Commits](Azure/azure-service-operator@v2.9.0...v2.11.0)

---
updated-dependencies:
- dependency-name: github.com/Azure/azure-service-operator/v2
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/Azure/azure-service-operator/v2-2.11.0 branch from bb5a496 to f34295c Compare November 19, 2024 01:08
@k8s-ci-robot
Copy link
Contributor

@dependabot[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-cluster-api-provider-azure-build f34295c link true /test pull-cluster-api-provider-azure-build
pull-cluster-api-provider-azure-test f34295c link true /test pull-cluster-api-provider-azure-test
pull-cluster-api-provider-azure-e2e-aks f34295c link true /test pull-cluster-api-provider-azure-e2e-aks
pull-cluster-api-provider-azure-capi-e2e f34295c link false /test pull-cluster-api-provider-azure-capi-e2e
pull-cluster-api-provider-azure-e2e f34295c link true /test pull-cluster-api-provider-azure-e2e
pull-cluster-api-provider-azure-verify f34295c link true /test pull-cluster-api-provider-azure-verify

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@mboersma
Copy link
Contributor

/hold

We are constrained here by the common dependency of controller-runtime between CAPI and ASO. We can wait for CAPI to upgrade, or we can try to do some go.mod replace hackery.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
Status: Todo
Development

Successfully merging this pull request may close these issues.

2 participants