cluster-api-provider-azure icon indicating copy to clipboard operation
cluster-api-provider-azure copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Add new upstream e2e test specs from CAPI

Open mboersma opened this issue 2 years ago • 6 comments

/kind feature

Describe the solution you'd like

In the CAPI 1.2.0 release, several new e2e test specs were added. We already run many of those upstream test specs in capi_test.go, and any new ones that make sense should be added to the test suite.

See this comment in PR #2431 for more detail.

Anything else you would like to add:

mboersma avatar Aug 11 '22 15:08 mboersma

/help

mboersma avatar Aug 11 '22 15:08 mboersma

@mboersma: This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to this:

/help

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-ci-robot avatar Aug 11 '22 15:08 k8s-ci-robot

/assign

sayantani11 avatar Aug 25 '22 15:08 sayantani11

/milestone v1.6

CecileRobertMichon avatar Sep 29 '22 16:09 CecileRobertMichon

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

k8s-triage-robot avatar Feb 08 '23 12:02 k8s-triage-robot

/remove-lifecycle stale

mboersma avatar Feb 08 '23 13:02 mboersma