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

Track Ready Pods in Job status #2879

Open
8 tasks done
alculquicondor opened this issue Aug 19, 2021 · 21 comments
Open
8 tasks done

Track Ready Pods in Job status #2879

alculquicondor opened this issue Aug 19, 2021 · 21 comments
Assignees
Labels
sig/apps Categorizes an issue or PR as relevant to SIG Apps. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@alculquicondor
Copy link
Member

alculquicondor commented Aug 19, 2021

Enhancement Description

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

alculquicondor commented Aug 19, 2021

/assign
/sig apps

@k8s-ci-robot k8s-ci-robot added sig/apps Categorizes an issue or PR as relevant to SIG Apps. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Aug 19, 2021
@alculquicondor alculquicondor changed the title Track Running Pods in Job status Track Ready Pods in Job status Aug 19, 2021
@salaxander
Copy link

salaxander commented Sep 1, 2021

/milestone v1.23

@k8s-ci-robot k8s-ci-robot added this to the v1.23 milestone Sep 1, 2021
@salaxander salaxander added stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Sep 1, 2021
@salaxander
Copy link

salaxander commented Sep 1, 2021

Hi @alculquicondor! 1.23 Enhancements team here. Just checking in as we approach enhancements freeze on Thursday 09/09. Here's where this enhancement currently stands:

  • KEP file using the latest template has been merged into the k/enhancements repo.
  • [X ] KEP status is marked as implementable
  • [X ] KEP has a test plan section filled out.
  • [X ] KEP has up to date graduation criteria.
  • [ X] KEP has a production readiness review that has been completed and merged into k/enhancements.

Looks like for this one we would just need the KEP to merge by enhancements freeze :)

Thanks!

@jlbutler
Copy link

jlbutler commented Sep 22, 2021

Hi @alculquicondor 👋 1.23 Docs lead here.

This enhancement is marked as 'Needs Docs' for the 1.23 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.23 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu November 18, 11:59 PM PDT.

Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thanks!

@chrisnegus
Copy link

chrisnegus commented Nov 17, 2021

Hi @alculquicondor 👋 1.23 Docs shadow here.
This enhancement is marked as ‘Needs Docs’ for the 1.23 release.
Please follow the steps detailed in the documentation to open a PR against the dev-1.23 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu November 18, 11:59 PM PDT.
Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.
Thanks!

@reylejano
Copy link
Member

reylejano commented Nov 19, 2021

Hi @alculquicondor and @kubernetes/sig-apps-misc ,
1.23 Release Lead here. We're a day past the 1.23 Docs Placeholder PR deadline and this enhancement is marked as 'Needs Docs' for 1.23 and is without a linked Doc PR to the dev-1.23 branch in k/website.

Since this feature is going to be alpha in 1.23, is this enhancement feature-gated? Does the Feature Gates page need to be updated with this enhancement? Does other documentation on kubernetes.io need to be updated or created? If so, please create a PR to the dev-1.23 branch in k/website ASAP

@alculquicondor
Copy link
Member Author

alculquicondor commented Nov 22, 2021

The PR is up. Sorry about the delay. I missed this before going on vacation.

@chrisnegus
Copy link

chrisnegus commented Nov 22, 2021

The PR is up. Sorry about the delay. I missed this before going on vacation.

Not a problem. Thanks so much for getting this done! Is the feature gate information all that needs to be updated or are more docs needed? If that's it, I'll work on getting it looked at and merged.

@alculquicondor
Copy link
Member Author

alculquicondor commented Nov 22, 2021

that's all that's needed. The rest is already part of the API reference.

@gracenng gracenng 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 Jan 9, 2022
@gracenng gracenng removed this from the v1.23 milestone Jan 9, 2022
@soltysh
Copy link
Contributor

soltysh commented Jan 18, 2022

/milestone v1.24

@k8s-ci-robot k8s-ci-robot added this to the v1.24 milestone Jan 18, 2022
@gracenng gracenng added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Jan 22, 2022
@gracenng
Copy link
Member

gracenng commented Jan 22, 2022

Hi @alculquicondor ! 1.24 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd. This enhancements is targeting beta for 1.24
Here’s where this enhancement currently stands:

  • Updated KEP file using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable for this release with latest-milestone: 1.24
  • KEP has a test plan section filled out.
  • KEP has up to date graduation criteria.
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

The status of this enhancement is track as tracked. I think there's a mistake in this issue description, it should be beta instead of stable right?
Thanks!

@alculquicondor
Copy link
Member Author

alculquicondor commented Jan 24, 2022

KEP PR is merged and description is up to date

@mehabhalodiya
Copy link

mehabhalodiya commented Feb 22, 2022

Hi @alculquicondor 👋🏻 1.24 Docs shadow here.
The Docs status for this enhancement is marked as 'None Required' for the 1.24 release.
Are you targeting any changes that would affect docs for this KEP for the upcoming 1.24 release?
Please confirm.
Thanks!

@alculquicondor
Copy link
Member Author

alculquicondor commented Feb 22, 2022

Yes, we just need to update the graduation status to beta.

@mehabhalodiya
Copy link

mehabhalodiya commented Feb 22, 2022

@alculquicondor Please follow the steps detailed in the documentation to open a PR against the dev-1.24 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu March 31, 11:59 PM PDT.

Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thanks!

@hosseinsalahi
Copy link

hosseinsalahi commented Mar 21, 2022

Hello @alculquicondor

I'm just checking in once more as we approach the 1.24 Code Freeze on 18:00 PDT, Tuesday, March 29th 2022

Please ensure the following items are completed:

For note, the status of this enhancement is currently marked as at risk.

Could you please confirm if following PR is part of the implementation for this enhancement?

Kindly please let me know if I'm missing any related PRs other than the ones I linked above. Thank you so much!

@alculquicondor
Copy link
Member Author

alculquicondor commented Mar 21, 2022

yes, they are both part of the enhancement and there are no more PRs.

@alculquicondor
Copy link
Member Author

alculquicondor commented Mar 21, 2022

Added documentation PR

@Priyankasaggu11929 Priyankasaggu11929 removed this from the v1.24 milestone May 10, 2022
@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
@janetkuo janetkuo added stage/beta Denotes an issue tracking an enhancement targeted for Beta status and removed stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels May 13, 2022
@janetkuo
Copy link
Member

janetkuo commented May 13, 2022

@Priyankasaggu11929 I changed the stage to beta. Should we mark this tracked in 1.24?

@k8s-triage-robot
Copy link

k8s-triage-robot commented Aug 11, 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 11, 2022
@alculquicondor
Copy link
Member Author

alculquicondor commented Aug 11, 2022

/remove-lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/apps Categorizes an issue or PR as relevant to SIG Apps. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
None yet
Development

No branches or pull requests