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

Use kubectl to view logs of system services on nodes #2258

Open
1 of 4 tasks
aravindhp opened this issue Jan 12, 2021 · 48 comments
Open
1 of 4 tasks

Use kubectl to view logs of system services on nodes #2258

aravindhp opened this issue Jan 12, 2021 · 48 comments
Assignees
Labels
sig/windows Categorizes an issue or PR as relevant to SIG Windows. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@aravindhp
Copy link
Contributor

aravindhp commented Jan 12, 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 Jan 12, 2021
@aravindhp
Copy link
Contributor Author

aravindhp commented Jan 12, 2021

/cc @LorbusChris @marosset @immuzz
/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 Jan 12, 2021
@marosset marosset added this to In Progress (v1.21) in SIG-Windows Jan 14, 2021
@dougsland
Copy link
Member

dougsland commented Jan 27, 2021

/cc

@annajung annajung 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 Jan 28, 2021
@annajung annajung added this to the v1.21 milestone Jan 28, 2021
@annajung
Copy link
Member

annajung commented Feb 7, 2021

Hi @aravindhp

Enhancements Freeze is 2 days away, Feb 9th EOD PST

Enhancements team is aware that KEP update is currently in progress (PR #2271). Please make sure PR merges 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.

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

@aravindhp
Copy link
Contributor Author

aravindhp commented Feb 7, 2021

@annajung #2271 has the following completed:
[IN PROGRESS] The KEP must have test plans
[IN PROGRESS] The KEP must have graduation criteria
[IN PROGRESS] The KEP must have a production readiness review (I need update the check mark but it has been /approved for PRR)
Is there a reason for it to be marked IN PROGRESS?

@annajung
Copy link
Member

annajung commented Feb 7, 2021

@aravindhp We consider it in progress until PR merges. Even if you have a PR open for the change, if it doesn't merge before the enhancements freeze, this enhancement is at risk of not making it into the release.

@aravindhp
Copy link
Contributor Author

aravindhp commented Feb 7, 2021

Thanks for the clarification @annajung. We are waiting for LGTMs from sig-node and sig-auth to merge.

@annajung
Copy link
Member

annajung commented Feb 10, 2021

Hi @aravindhp,

Enhancements Freeze is now in effect.

Unfortunately, your KEP needed to be updated and the PR has not yet merged. If you wish to be included in the 1.21 Release, please submit an Exception Request as soon as possible.

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.21 milestone Feb 10, 2021
@annajung annajung 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 Feb 10, 2021
@immuzz
Copy link

immuzz commented Feb 19, 2021

This is very much needed especially for scenarios where you need to access host like gMSA for Windows Containers. Cant wait to see this land soon

@marosset marosset moved this from In Progress (v1.21) to InProgress (v1.22) in SIG-Windows Mar 11, 2021
@JamesLaverack JamesLaverack 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 Apr 29, 2021
@JamesLaverack JamesLaverack added this to the v1.22 milestone May 3, 2021
@salaxander
Copy link

salaxander commented May 11, 2021

Hi @aravindhp , 1.22 enhancements team here!

For the enhancement to be included in the milestone, it must meet the following criteria:

[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

Looks like we're in good shape for enhancements freeze on 5/13. Let us know if there's anything we can do to help before then!

Thanks!!

@salaxander
Copy link

salaxander commented Jun 23, 2021

Hey @aravindhp - Just checking in as we're about 2 weeks away from 1.22 code freeze. Are there any open or merged k/k PRs we should be tracking for this? Thanks!

@aravindhp
Copy link
Contributor Author

aravindhp commented Jun 23, 2021

@salaxander, I have a WIP PR: kubernetes/kubernetes#96120. But it is looking very tight at this point.

@salaxander
Copy link

salaxander commented Jul 2, 2021

Hi @aravindhp - One more check-in as we're a week out from code freeze. Any updates on if you expect kubernetes/kubernetes#96120 to merge before the deadline?

Thanks!

@LorbusChris
Copy link
Contributor

LorbusChris commented Jul 2, 2021

By now, I don't think it's reasonable to assume it will make it in in time. We will circle back to this in the next Dev window.

@marosset marosset moved this from InProgress (v1.22) to In Progress (v1.23) in SIG-Windows Jul 29, 2021
@marosset
Copy link
Contributor

marosset commented Jul 29, 2021

/milestone clear

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 21, 2022

Hello @aravindhp 👋, just a quick check-in again, as we approach the 1.25 enhancements freeze.

Please plan to get the open PR #3341 merged before enhancements freeze on Thursday, June 23, 2022 at 18:00 PM PT. (which is just over 3 days away from now)

For note, the current status of the enhancement is atat-risk. Thank you!


Update on June 22, 2022

With KEP PR #3341 merged, the enhancement is ready for the 1.25 Enhancements Freeze. For note, the status is now marked as tracked.

@aravindhp
Copy link
Contributor Author

aravindhp commented Jun 21, 2022

@Priyankasaggu11929, #3341 has been merged.

@marosset
Copy link
Contributor

marosset commented Jul 25, 2022

Hi @aravindhp 👋

1.25 enhancements team here. Checking in once more as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 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.

I see the following PRs open

For now this enhancement is being tracked as at-risk

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

Thanks!!

@cathchu
Copy link

cathchu commented Jul 29, 2022

Hey there @aravindhp 👋 , 1.25 Release Docs Shadow here!

As a reminder, docs placeholder PRs are due August 4th. I see that this Enhancement has a placeholder docs PR originally for Release 1.24. Please point the 1.24 PR to 1.25 as discussed.

Also, take a look at Documenting a release for additional information for the docs requirement for the release.

Thanks!

@aravindhp
Copy link
Contributor Author

aravindhp commented Jul 29, 2022

As a reminder, docs placeholder PRs are due August 4th. I see that this Enhancement has a placeholder docs PR originally for Release 1.24. Please point the 1.24 PR to 1.25 as discussed.

@LorbusChris please take care of this I would have to open a new PR to change the branch.

@LorbusChris
Copy link
Contributor

LorbusChris commented Aug 1, 2022

@cathchu @aravindhp I've switched the base branch for kubernetes/website#32660

@marosset
Copy link
Contributor

marosset commented Aug 2, 2022

This was discussed at the SIG-Windows community meeting today and unfortunately implementation won't be ready by code freeze so this will get moved to v1.26

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.25 milestone Aug 2, 2022
@marosset marosset 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 Aug 17, 2022
@marosset marosset removed this from In Progress (v1.25) in SIG-Windows Aug 18, 2022
@aravindhp
Copy link
Contributor Author

aravindhp commented Aug 25, 2022

/assign

@marosset
Copy link
Contributor

marosset commented Sep 12, 2022

/label lead-opted-in

@k8s-ci-robot k8s-ci-robot added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 12, 2022
@rhockenbury rhockenbury 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 Sep 18, 2022
@rhockenbury
Copy link

rhockenbury commented Sep 18, 2022

Hello @aravindhp 👋, 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.

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

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

@marosset
Copy link
Contributor

marosset commented Oct 31, 2022

Hi @aravindhp 👋,

Checking in once more as we approach 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!

@cathchu
Copy link

cathchu commented Nov 2, 2022

Hi there @aravindhp 👋 1.26 Docs Shadow here.

This enhancement is marked as ‘Needs Docs’ for 1.26 release. I see you've opened kubernetes/website#32660. I'd like to confirm that all Docs related changes will be included in this PR.

If not, 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!

@marosset
Copy link
Contributor

marosset commented Nov 7, 2022

Hi @aravindhp 👋,

Checking in once more as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.

Please ensure the following items are completed:

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

@rhockenbury
Copy link

rhockenbury commented Nov 9, 2022

Hello 👋, 1.26 Enhancements Lead here

Unfortunately, this enhancement did not meet requirements for code freeze.
If you still wish to progress this enhancement in v1.26, please file an exception request. Thanks!

/milestone clear
/label tracked/no
/remove-label tracked/yes
/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Nov 9, 2022
@k8s-ci-robot k8s-ci-robot removed this from the v1.26 milestone Nov 9, 2022
@k8s-ci-robot k8s-ci-robot removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team lead-opted-in Denotes that an issue has been opted in to a release labels Nov 9, 2022
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. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
Status: Net New
Status: In Progress
Development

No branches or pull requests