search

kubernetes-sigs / sig-windows-tools

Repository for tools and artifacts related to the sig-windows charter in Kubernetes. Scripts to assist kubeadm and wincat and flannel will be hosted here.
Apache License 2.0
122 stars 123 forks source link

docs: tracking issue for adding various guides under /guides #255

Closed profnandaa closed 6 months ago

profnandaa commented 1 year ago

This is a tracking issue to add various useful guides related to Windows on Kubernetes. Can really be anything. Please feel free to suggest here guides that need to be added.

TODO:

profnandaa commented 1 year ago

/assign @profnandaa

jsturtevant commented 1 year ago

xref: https://github.com/kubernetes-sigs/sig-windows-tools/issues/217

These are great ideas! If possible, would like to see docs go into the upstream repositories to lower the maintenance on sig-windows.

profnandaa commented 1 year ago

@jsturtevant -- possible to have them here as an incubator/WIP and then move them over to upstream once "matured"? Or do we run a risk of more management overhead? :thinking:

jsturtevant commented 1 year ago

once they get merged here, they get used and then we get lots of folks trying them out (this has happened with all the CNI work). Since we aren't always the experts on the surrounding technology it becomes difficult to help and folks get frustrated.

Don't get me wrong I think these are fantastic things for us to help contribute back to projects to make it easier for Windows users. Using this repo as a way to track and plan works for me. Also having a list where we can point them out to all the new docs would be good too.

profnandaa commented 1 year ago

@jsturtevant -- got it, makes sense.

profnandaa commented 1 year ago

So, the guides section could just be hyper-links with brief commentaries, right?

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

marosset commented 1 year ago

/remove-lifecycle rotten

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 7 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 6 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 6 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/sig-windows-tools/issues/255#issuecomment-1951369408): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.