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

Published 20 hours ago • verified publisher icon kubernetes-sigs

Tracking: Drop `util/paused` once `v1beta2conditions` migration is complete.

Open theobarberbany opened this issue 8 months ago • 3 comments
trafficstars

/kind bug

#5383 added util/paused, which is pulled from upstream cluster-api but modified to not rely on v1beta2conditions. At the time of writing the upstream library requires v1beta2conditions, which CAPA has yet to implement.

Once CAPA has implemented v1beta2conditions (likely when they're just Conditions again after the migration) we should use the upstream package.

This issue is to track this, so we don't forget :)

theobarberbany avatar Mar 17 '25 14:03 theobarberbany

This issue is currently awaiting triage.

If CAPA/CAPI 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-sigs/prow repository.

k8s-ci-robot avatar Mar 17 '25 14:03 k8s-ci-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

k8s-triage-robot avatar Jun 15 '25 14:06 k8s-triage-robot

/remove-lifecycle stale

theobarberbany avatar Jun 16 '25 13:06 theobarberbany

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

k8s-triage-robot avatar Sep 14 '25 13:09 k8s-triage-robot

/remove-lifecycle stale

theobarberbany avatar Sep 15 '25 09:09 theobarberbany