Web UI doesn't support node status modification

[sivchari]

Since I wanna assign many pods to node, I edited allocatable and capacity in node status.

This operation can be done via kubectl, but it can't via Web UI. I guess that Web UI only supports to edit any spec. Thus, to make it possible, we need to request to /${resources}/status endpoint, too.

[sanposhiho]

When I edited node resource,

From this case is happened with Pod

Which resource did you edit? Can you provide us with any repro steps?

[sivchari]

Sure, I'd give you some steps to reproduce 👍

[sivchari]

Hi, @sanposhiho Since I wanna assign many pods to node, I edited allocatable and capacity in /status. But the changes weren't applied. This change can be made in kubectl, not in the Web UI.

I used the fllowing command. kwokctl kubectl edit node node-fp2l5 -n default --subresource='status'

I guess that /status can only be edited with using --subresource flag. If kube-scheduler-simulator needs to deal with this, it will be simple changes. What do you think ? Thanks. kwokctl kubectl edit node node-xxx -n default --subresource='status'

[sanposhiho]

Got you. So you meant -

/retitle Web UI doesn't support node status modification /area web

[sanposhiho]

Can you clarify the description on the top too; now it's very unclear

[sivchari]

I revised the description, thanks.

[k8s-triage-robot]

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

This bot triages un-triaged 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:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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:

• 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

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

/close not-planned

[k8s-ci-robot]

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

In response to this:

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

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

/close not-planned

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-sigs/prow repository.