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

OpenAPI v3 for kubectl explain #3515

Open
4 tasks done
alexzielenski opened this issue Sep 14, 2022 · 8 comments
Open
4 tasks done

OpenAPI v3 for kubectl explain #3515

alexzielenski opened this issue Sep 14, 2022 · 8 comments
Assignees
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/cli Categorizes an issue or PR as relevant to SIG CLI. 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
Milestone

Comments

@alexzielenski
Copy link
Contributor

alexzielenski commented Sep 14, 2022

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 Sep 14, 2022
@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 16, 2022

@alexzielenski please provide a Discussion Link. It is required that you "link to SIG mailing list thread, meeting, or recording where the Enhancement was discussed before KEP creation"

@KnVerey KnVerey added sig/cli Categorizes an issue or PR as relevant to SIG CLI. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status lead-opted-in Denotes that an issue has been opted in to a release labels Sep 30, 2022
@k8s-ci-robot k8s-ci-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Sep 30, 2022
@rhockenbury
Copy link

rhockenbury commented Oct 1, 2022

/milestone v1.26
/label tracked/yes

@k8s-ci-robot k8s-ci-robot added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Oct 1, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.26 milestone Oct 1, 2022
@rhockenbury
Copy link

rhockenbury commented Oct 3, 2022

Hello @alexzielenski 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26 (correct me, if otherwise)

Here's where this enhancement currently stands:

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

For this KEP, we would just need to get #3516 merged up to meet the requirements.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

@alexzielenski
Copy link
Contributor Author

alexzielenski commented Oct 6, 2022

@rhockenbury The PR has been merged with PRR and I think satisfies the checklist. Please let me know if there is anything left to do!

@rhockenbury
Copy link

rhockenbury commented Oct 6, 2022

Thanks. With #3516 merged, this enhancement is all set for enhancements freeze.

@cathchu
Copy link

cathchu commented Nov 2, 2022

Hello @alexzielenski 👋 1.26 Release Docs shadow here!

This enhancement is marked as ‘Needs Docs’ for 1.26 release. Please follow the steps detailed in the documentation to open a PR against dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

@ruheenaansari34
Copy link

ruheenaansari34 commented Nov 2, 2022

Hi @alexzielenski 👋,

Checking in once more as we approach the 1.26 code freeze at 17:00 PDT on Tuesday 8th November 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 enhancement, it looks like the following PRs are open and need to be merged before code freeze:

As always, we are here to help should questions come up. Thanks!

@ruheenaansari34
Copy link

ruheenaansari34 commented Nov 7, 2022

For this enhancement, it looks like the k/k PR kubernetes/kubernetes#113146 is closed.

  • If you do have any other k/k PRs open, please link them to this issue.
  • Please ensure that PRs are linked in the above issue description as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/cli Categorizes an issue or PR as relevant to SIG CLI. 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
Projects
Status: Net New
Development

No branches or pull requests

7 participants