CAPI v1.7.0-beta.0 has been released and is ready for testing

[nawazkh]

CAPI v1.7.0-beta.0 has been released and is ready for testing.
Looking forward to your feedback before v1.7.0 release!

For quick reference

• CAPI v1.7.0-beta.0 release notes
• Shortcut to CAPI git issues

Following are the planned dates for the upcoming releases

CAPI v1.7.0 will be released on Tuesday, 16th April 2024.

More details of the upcoming schedule can be seen at CAPI v1.7.0 release timeline.

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI Operator contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[furkatgofurov7]

Covered in #493

/close

[k8s-ci-robot]

@furkatgofurov7: Closing this issue.

In response to this:

Covered in #493

/close

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.