/sig cli

#2189 is updated now as well as the PR #97099.
/assign

@dougsland @howardjohn Thanks for review of the KEP. What would be the next step for this? I'm not quite familiar with the process.

#2189 is updated now as well as the PR #97099.
/assign

@dougsland @howardjohn Thanks for review of the KEP. What would be the next step for this? I'm not quite familiar with the
process.

I have added the enhancement #2189 to SIG Cli agenda asking people to take a look when they have free time. We need more people to review.

Hey,

We have #2227 and #2368 , what is the difference between them?

@rikatz I closed #2368 and will update the KEP pr.

/stage alpha
/milestone v1.21
/kind feature

Greetings @pacoxu,

This is Joseph v1.21 enhancement shadow checking in. For the enhancement to be included in the 1.21 milestone, it must meet the following criteria:

The KEP must be merged in an implementable state
The KEP must have test plans
The KEP must have graduation criteria
The KEP must have a production readiness review

Starting v1.21, all KEPs must include a production readiness review. Please make sure to take a look at the instructions and update the KEP to include all steps. Let us know if we can be of any assistance.

Thank you!

@jrsapi the enhancement is approved both by sig-leads and PRR approvers, it's awaiting small update and should merge on time.

Greetings @soltysh @pacoxu,
Thanks for the update. Reminder that enhancement freeze is 2 days away, Feb 9th EOD PST

Enhancements team is aware that KEP update is currently in progress (PR [#2189]. Please make sure the updates get done and pr merged before the freeze. For PRR related questions or to boost the PR for PRR review, please reach out in slack #prod-readiness

Any enhancements that do not complete the following requirements by the freeze will require an exception.

[DONE] The KEP must be merged in an implementable state
[DONE] The KEP must have test plans
[DONE] The KEP must have graduation criteria
[DONE] The KEP must have a production readiness review

/assign

[IN PROGRESS] The KEP must have a production readiness review

@jrsapi #2189 merged on Friday with PRR approved, what else is missing?

@soltysh Verified the kep.yaml for PRR. We're good to go. Thanks for your efforts and patience with this new step.

Greetings @pacoxu,
Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:
• Tuesday, March 9th: Week 9 - Code Freeze
• Tuesday, March 16th: Week 10 - Docs Placeholder PR deadline
• If this enhancement requires new docs or modification to existing docs, please follow the steps in the Open a placeholder PR doc to open a PR against k/website repo.
As a reminder, please link all of your k/k PR(s) and k/website PR(s) to this issue so we can track them.
Thanks!

kubernetes/kubernetes#97099 is ready for log and exec.

I will work on it late next week and the first week of March.

Thanks for reminding @jrsapi

/assign @mengjiao-liu

@pacoxu: GitHub didn't allow me to assign the following users: mengjiao-liu.

Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

I will work in cp, which will be finished this week.

@ingvagabund @pacoxu even though the annotation was removed, this functionality wasn't officially GA-ed, so I'd suggest in 1.26 to promote this to stable.

@soltysh what do we need to do to promote to stable in this case? I moved to 1.27 because we didn't make the opt-in period for 1.26.

thanks. We may update it to be GAed in v1.27 release cycle.

@soltysh what do we need to do to promote to stable in this case? I moved to 1.27 because we didn't make the opt-in period for 1.26.

sgtm - thx!

/label lead-opt-in

@soltysh: The label(s) /label lead-opt-in cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, lead-opted-in, tracked/no, tracked/out-of-tree, tracked/yes. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

/label lead-opted-in

Hello @pacoxu 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage stable for v1.27 (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: v1.27
• 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 enhancement it looks like #3457 will address all of the remaining 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!

#3457 is waiting for prr approval.

• there will be no k/k or k/website pr for this, IMO.

For graduation to GA, we should document kubectl.kubernetes.io/default-logs-container as deprecated. See https://kubernetes.io/docs/reference/labels-annotations-taints/ - it's not there yet.

Also, ideally, we wait a couple of releases between documenting the deprecation and dropping the support.

For graduation to GA, we should document kubectl.kubernetes.io/default-logs-container as deprecated. See https://kubernetes.io/docs/reference/labels-annotations-taints/ - it's not there yet.

• kubectl.kubernetes.io/default-logs-container was deprecated in v1.21 when we add kubectl.kubernetes.io/default-container
• kubectl.kubernetes.io/default-logs-container support was removed in v1.25

https://github.com/kubernetes/website/pull/27095/files

• kubectl.kubernetes.io/default-logs-container has not been added to the document ever
• The PR above add kubectl.kubernetes.io/default-container since v1.21

I agree with those things, and we should document the deprecated annotation. Graduation to GA is a trigger point for checking we didn't miss a detail; it turns out that we did.

Once we register an annotation, even as deprecated or no longer respected, we leave it documented forever.

With #3457 merged I'm marking this enhancement as tracked for v1.27.

/remove-label tracked/no
/label tracked/yes

Hello @pacoxu 👋🏾 !

@katmutua 1.27 Release Docs shadow here. This enhancement is marked as ‘Needs Docs’ for 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.

If you already have existing open PRs please link them to the description so we can easily track them. Thanks!

I agree with those things, and we should document the deprecated annotation. Graduation to GA is a trigger point for checking we didn't miss a detail; it turns out that we did.

Once we register an annotation, even as deprecated or no longer respected, we leave it documented forever.

I opened kubernetes/website#39899.

Hi @pacoxu 👋,
Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.
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.
  • add e2e test for kubectl default container annotation kubernetes#115046

Please let me know what other PRs in k/k I should be tracking for this KEP.
As always, we are here to help should questions come up. Thanks!

If I understand correctly only kubernetes/kubernetes#115046 and kubernetes/website#39899 are merged for v1.27.
And there are no todo items for this KEP.

We usually wait until the code-freeze to check with the authors if there are any more PR's left to acknowledge and merge. And since its now past the code-freeze and there are no action items for this KEP, we can close it :)

/close

@Atharva-Shinde: Closing this issue.

/remove-label lead-opted-in