kube-scheduler-simulator icon indicating copy to clipboard operation
kube-scheduler-simulator copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Reset function completely deletes all resources, including system's priorityclass

Open 196Ikuchil opened this issue 2 years ago • 2 comments

Problem

The reset function completely deletes all resources, including the system's priorityclass.

After the simulator is launched, these two PriorityClass, system-cluster-critical and system-node-critical, are created automatically. But this Reset function removes these from the simulator, too. I think that these two PriorityClass should be kept.

↓After the RESET. screenshot

196Ikuchil avatar Apr 18 '22 16:04 196Ikuchil

/triage accepted Not to mark as stale.

sanposhiho avatar Jun 07 '22 10:06 sanposhiho

/area web

sanposhiho avatar Sep 04 '22 03:09 sanposhiho

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-triage-robot avatar Dec 03 '22 03:12 k8s-triage-robot

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-triage-robot avatar Jan 02 '23 04:01 k8s-triage-robot

/remove-lifecycle rotten /lifecycle frozen

sanposhiho avatar Jan 17 '23 01:01 sanposhiho

This issue already has been resolved in #229

/close

196Ikuchil avatar May 30 '23 14:05 196Ikuchil

@196Ikuchil: Closing this issue.

In response to this:

This issue already has been resolved in #229

/close

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 avatar May 30 '23 14:05 k8s-ci-robot