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.

Sign up for GitHub

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

Jump to bottom

Overhaul Windows documentation #31428

Open
9 of 31 tasks
marosset opened this issue Jan 20, 2022 · 24 comments
Open
9 of 31 tasks

Overhaul Windows documentation #31428

marosset opened this issue Jan 20, 2022 · 24 comments
Labels
language/en Issues or PRs related to English language lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/windows Categorizes an issue or PR as relevant to SIG Windows. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@marosset
Copy link
Contributor

marosset commented Jan 20, 2022 •
edited
Loading

This issue will track a number of improvements SIG-Windows would like to make to the windows documentation.

(I'll continue to update this list over the next few days)

/milestone v1.24
/sig windows
@marosset marosset added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 20, 2022
@k8s-ci-robot
Copy link
Contributor

@marosset: You must be a member of the kubernetes/website-milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Website milestone maintainers and have them propose you as an additional delegate for this responsibility.

In response to this:

This issue will track a number of improvements SIG-Windows would like to make to the windows documentation.

(I'll continue to update this list over the next few days)

/milestone v1.24
/sig windows

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 added sig/windows Categorizes an issue or PR as relevant to SIG Windows. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 20, 2022
@marosset
Copy link
Contributor Author

/cc @brasmith-ms @jsturtevant @jayunit100 @claudiubelu @aravindhp

@jihoon-seo
Copy link
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 21, 2022
@tengqm
Copy link
Contributor

tengqm commented Jan 21, 2022

Thank you for filing an umbrella issue before working on it.

@sftim
Copy link
Contributor

sftim commented Jan 21, 2022

This looks like a partial duplicate of #29769

We should close one of these, I think.
/language en
/remove-kind feature

@k8s-ci-robot k8s-ci-robot added language/en Issues or PRs related to English language and removed kind/feature Categorizes issue or PR as related to a new feature. labels Jan 21, 2022
@sftim sftim mentioned this issue Jan 21, 2022
Closed
@sftim
Copy link
Contributor

sftim commented Jan 21, 2022

Much of https://kubernetes.io/docs/setup/production-environment/windows/intro-windows-in-kubernetes/ does not belong in the “production environment” section; it's not specific to deploying into production.
We should identify sections of that page to migrate elsewhere.

When moving existing content around, please add the “refactor” label to the PRs - or highlight to a reviewer that this label needs adding. That label helps localization teams spot when apparently-new content is actually being reused.

@sftim
Copy link
Contributor

sftim commented Jan 21, 2022

/priority important-longterm

@k8s-ci-robot k8s-ci-robot added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Jan 21, 2022
@brasmith-ms brasmith-ms mentioned this issue Jan 21, 2022
Closed
@jsturtevant jsturtevant mentioned this issue Jan 21, 2022
Closed
@jihoon-seo jihoon-seo mentioned this issue Jan 26, 2022
Closed
This was referenced Feb 22, 2022
Merged
Merged
Closed
Closed
@aravindhp aravindhp mentioned this issue Feb 25, 2022
Closed
@neolit123 neolit123 mentioned this issue Mar 16, 2022
Closed
This was referenced Mar 31, 2022
Closed
Closed
Closed
@jihoon-seo jihoon-seo mentioned this issue Jul 11, 2022
Closed
@jihoon-seo jihoon-seo mentioned this issue Jul 27, 2022
Merged
20 tasks
@k8s-triage-robot
Copy link

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 Sep 5, 2022
@aravindhp
Copy link
Contributor

/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 Sep 6, 2022
@aravindhp
Copy link
Contributor

@marosset I have reviewed configure-runasusername. I don't see anything missing. I don't see a reason to link to projected volumes and Windows RunAsUsername securitycontext-interactions. Folks who are using projected volumes would read that page and will become aware of the limitation.

@k8s-triage-robot
Copy link

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 Dec 13, 2022
@sftim
Copy link
Contributor

sftim commented Dec 14, 2022

@marosset, would you consider these docs overhauled?

@k8s-triage-robot
Copy link

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:

  • Mark this issue or PR as fresh with /remove-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 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 Jan 13, 2023
@sftim
Copy link
Contributor

sftim commented Jan 13, 2023

/remove-lifecycle rotten

Query not yet answered. Anyone from SIG Windows is welcome to answer it.

@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 Jan 13, 2023
@sftim
Copy link
Contributor

sftim commented May 2, 2023

How's this work going?

@sftim
Copy link
Contributor

sftim commented Jul 24, 2023

/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 Jul 24, 2023
@aravindhp
Copy link
Contributor

@sftim sorry about the late response. I brought this up at today's sig-windows meeting. We decided to make this a rolling agenda item that will be discussed every week when we have a light agenda. Hopefully that will attract more contributors and we can move forward with improving the Windows docs.

@aravindhp
Copy link
Contributor

To kick things off with https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes/ we are going to wait on #34476 (comment) that calls out that the Linux sections need to get filled in.

@aravindhp
Copy link
Contributor

@tzifudzi will take up Specify minimum or recommended system requirements.

@tzifudzi tzifudzi mentioned this issue Aug 12, 2023
Merged
@sftim
Copy link
Contributor

sftim commented Jan 31, 2024

Also see #44964

This was referenced Sep 10, 2024
Closed
Merged
@neolit123
Copy link
Member

note:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
language/en Issues or PRs related to English language lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/windows Categorizes an issue or PR as relevant to SIG Windows. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
[sig-windows] Issue Tracking
Status: No status
Milestone
No milestone
Development

No branches or pull requests
8 participants
@neolit123 @tengqm @aravindhp @marosset @k8s-ci-robot @sftim @jihoon-seo @k8s-triage-robot