More info in JIRA, but blocked on creation of setting

Removed assignments, anyone can pick this up once setting available

The backend PR has been merged, and the changes are now available in the latest docker.io/rancher/rancher:head image. This should no longer be a blocker for the UI.

cc @richard-cox

The theory is that the Steve API should report the min/max values. However, @kwwii may have some design questions, especially if the Global Settings page is the right home.

@richard-cox can you confirm that this belongs on Global Settings? and are there any other limitations for UI that need to factor in that weren't documented?

Feature complete comes up very soon here so if this is needed for 2.10.0, we can step over a bit unless it's super clear to others closer to the ticket may indicate how quick it'll be.

This is a setting to assist a short term feature applicable to bulk updates to downstream clusters that have had their kube version bumped and was discussed in the RFC. I would vote we add this to general settings, but remove it after 2.12 (and update docs)

@jiaqiluo will the backend validate the input? Is there a min/max value to consider?

Hi @gaktive, the backend does not validate the input. The minimum should be 1, and there is no maximum. Could UI validate the input?

@jiaqiluo we can add some constraints on the UI side, but I believe the backend should always have the validation in place in case the request is not coming from the UI.

Also have a question, is the type integer or string?

Edit: Seems for all the other settings that are numbers a string value gets sent to the backend. I'll follow the same behaviour.

@momesgin, the backend will attempt the convert the string into an integer, or use the default value if the conversation fails. See code