kubesphere icon indicating copy to clipboard operation
kubesphere copied to clipboard

failed to edit the default container limitrange when there is a limitrange in namespace.

Open yangzan0816 opened this issue 3 years ago • 9 comments

问题描述: 编辑默认容器配额时,报pod无法建立默认限制的异常 image 运行环境: v3.2.1

yangzan0816 avatar Jun 01 '22 07:06 yangzan0816

Is there a limitrange named nprod-limit-range in the namespace? Can you provide the yaml of the limitrange.

If there is a limitrange in the namespace and then edit the default limit range in ks-consle. There will be an error like this.

apiVersion: v1
kind: LimitRange
metadata:
  name: test
  namespace: test
spec:
  limits:
  - max:
      cpu: "2"
      memory: "2Gi"
    type: Pod

/priority medium /cc @wansir

xyz-li avatar Jun 01 '22 07:06 xyz-li

yes, there is a limitrange in the namespace, 3q

yangzan0816 avatar Jun 01 '22 08:06 yangzan0816

/reopen

xyz-li avatar Jun 01 '22 08:06 xyz-li

@xyz-li: Reopened this issue.

In response to this:

/reopen

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.

ks-ci-bot avatar Jun 01 '22 08:06 ks-ci-bot

This is a bug.

xyz-li avatar Jun 01 '22 08:06 xyz-li

/kind bug

xyz-li avatar Jun 01 '22 08:06 xyz-li

Currently, the limit range created through the UI type always containers, we need to consider about this.

/assign @VioZhang

wansir avatar Jun 01 '22 08:06 wansir

/milestone BackLog

wansir avatar Jun 01 '22 08:06 wansir

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

stale[bot] avatar Sep 09 '22 00:09 stale[bot]

This issue is being automatically closed due to inactivity.

stale[bot] avatar Oct 12 '22 09:10 stale[bot]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

stale[bot] avatar Jan 16 '23 00:01 stale[bot]

This issue is being automatically closed due to inactivity.

stale[bot] avatar Apr 02 '23 03:04 stale[bot]