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

simplify sig-windows docs #29769

Closed
jayunit100 opened this issue Sep 21, 2021 · 4 comments
Closed

simplify sig-windows docs #29769

jayunit100 opened this issue Sep 21, 2021 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@jayunit100
Copy link
Member

This is a Bug Report

Problem:

We currently have copious references to flannel, wins, etc in the getting started w/ windows stuff.

  • hostProcess containers will obviate the need to use kube-proxy over wins
  • for now nssm is a easy, commonly done solution

Proposed Solution:

Clean out docs to just use a commonly supported, easily reproduced recipe for windows bootstrapping.
@jayunit100 jayunit100 added the kind/bug Categorizes issue or PR as related to a bug. label Sep 21, 2021
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 21, 2021
@sftim sftim mentioned this issue Sep 22, 2021
Merged
@kbhawkey
Copy link
Contributor

/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 Sep 24, 2021
@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 23, 2021
@sftim sftim mentioned this issue Jan 21, 2022
Open
31 tasks
@jsturtevant
Copy link
Contributor

/close
in favor of #31428 which has more details

@k8s-ci-robot
Copy link
Contributor

@jsturtevant: Closing this issue.

In response to this:

/close
in favor of #31428 which has more details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@jsturtevant @jayunit100 @kbhawkey @k8s-ci-robot @k8s-triage-robot