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

A Windows-[operational readiness] definition and tooling convergence #2578

Open
2 of 5 tasks
jayunit100 opened this issue Mar 19, 2021 · 28 comments · Fixed by #2975
Open
2 of 5 tasks

A Windows-[operational readiness] definition and tooling convergence #2578

jayunit100 opened this issue Mar 19, 2021 · 28 comments · Fixed by #2975
Assignees
Labels
sig/windows Categorizes an issue or PR as relevant to SIG Windows. tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@jayunit100
Copy link
Member

jayunit100 commented Mar 19, 2021

Enhancement Description

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 19, 2021
@jayunit100
Copy link
Member Author

jayunit100 commented Mar 19, 2021

/sig windows

@k8s-ci-robot k8s-ci-robot added sig/windows Categorizes an issue or PR as relevant to SIG Windows. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 19, 2021
@jayunit100
Copy link
Member Author

jayunit100 commented Mar 19, 2021

@marosset marosset added this to InProgress (v1.22) in SIG-Windows Mar 25, 2021
@fejta-bot
Copy link

fejta-bot commented Jun 17, 2021

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 17, 2021
@fejta-bot
Copy link

fejta-bot commented Jul 17, 2021

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 17, 2021
@marosset marosset moved this from InProgress (v1.22) to Backlog (v 1.23) in SIG-Windows Jul 29, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Aug 16, 2021

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

This bot triages issues and 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 issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Aug 16, 2021

@k8s-triage-robot: Closing this issue.

In response to this:

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

This bot triages issues and 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 issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

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

SIG-Windows automation moved this from Backlog (v 1.23) to Done (v1.23) Aug 16, 2021
@jayunit100 jayunit100 reopened this Aug 16, 2021
SIG-Windows automation moved this from Done (v1.23) to Backlog Aug 16, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Sep 15, 2021

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

This bot triages issues and 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 issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Sep 15, 2021

@k8s-triage-robot: Closing this issue.

In response to this:

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

This bot triages issues and 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 issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

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

SIG-Windows automation moved this from Backlog to Done (v1.23) Sep 15, 2021
@jayunit100
Copy link
Member Author

jayunit100 commented Sep 15, 2021

/reopen

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Sep 15, 2021

@jayunit100: Reopened this issue.

In response to this:

/reopen

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 k8s-ci-robot reopened this Sep 15, 2021
SIG-Windows automation moved this from Done (v1.23) to Backlog Sep 15, 2021
@jayunit100
Copy link
Member Author

jayunit100 commented Sep 15, 2021

#2975

@knabben
Copy link
Member

knabben commented Sep 15, 2021

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Sep 15, 2021
@gracenng gracenng added this to the v1.24 milestone Jan 14, 2022
@rhockenbury
Copy link

rhockenbury commented Jan 20, 2022

Hi @jayunit100! 1.24 Enhancements team here. Just checking in as we approach enhancements freeze at 18:00pm PT on Thursday Feb 3rd. This enhancement is targeting alpha for 1.24.

Here’s where this enhancement currently stands:

Please plan to merge #2975 before enhancements freeze to complete the list of items above.

The status of this enhancement is at risk. Thanks!

SIG-Windows automation moved this from Backlog to Done (v1.23) Jan 20, 2022
@rhockenbury
Copy link

rhockenbury commented Jan 20, 2022

Thanks all! With #2975 merged, I'm moving this to tracked for enhancement freeze.

@jayunit100
Copy link
Member Author

jayunit100 commented Jan 21, 2022

Thanks !

@marosset
Copy link
Contributor

marosset commented Jan 25, 2022

/reopen

@k8s-ci-robot k8s-ci-robot reopened this Jan 25, 2022
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Jan 25, 2022

@marosset: Reopened this issue.

In response to this:

/reopen

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.

SIG-Windows automation moved this from Done (v1.23) to Backlog Jan 25, 2022
@PI-Victor
Copy link
Member

PI-Victor commented Feb 19, 2022

hey folks, docs shadow here, are you targeting any changes that would affect docs for this KEP for the upcoming 1.24 release?

@rhockenbury
Copy link

rhockenbury commented Mar 22, 2022

Hi @jayunit100

I'm checking in as we approach 1.24 code freeze at 01:00 UTC Wednesday 30th March 2022.

Please ensure the following items are completed:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PRs are fully merged by the code freeze deadline.

For this KEP, it looks like there aren't any K/K PRs. Are there any other PRs that you think we should be tracking that would be subject to the 1.24 code freeze?

Let me know if you have any questions.

@rhockenbury
Copy link

rhockenbury commented Mar 29, 2022

Hi @jayunit100 - would you mind confirming that there are no k/k PRs required for this KEP for v1.24?

@jayunit100
Copy link
Member Author

jayunit100 commented Mar 29, 2022

yup , no k/k PRs , we will track this out of tree, and the only thing we need to track here is once the work is 100% completed, b/c then we will make changes in k/k to consume it in CI

@Priyankasaggu11929 Priyankasaggu11929 added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels May 10, 2022
@Priyankasaggu11929 Priyankasaggu11929 removed this from the v1.24 milestone May 10, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Aug 8, 2022

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

This bot triages issues and 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 issue is closed

You can:

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

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 8, 2022
@marosset
Copy link
Contributor

marosset commented Aug 8, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 8, 2022
@marosset
Copy link
Contributor

marosset commented Aug 8, 2022

This is being actively worked on.
https://github.com/kubernetes-sigs/windows-operational-readiness is the new home for this work.
Thanks @iXinqi !

@marosset marosset removed this from Backlog (issues) in SIG-Windows Sep 21, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Nov 23, 2022

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

This bot triages issues and 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 issue is closed

You can:

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

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

/lifecycle stale

@marosset
Copy link
Contributor

marosset commented Nov 28, 2022

/remove-lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/windows Categorizes an issue or PR as relevant to SIG Windows. tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
Development

Successfully merging a pull request may close this issue.