Background
This is a follow on story to be able to edit the workload requests and limits directly on the HPA form. Today we surface a warning when those fields are missing (which are both required to enable the utilization fields), and we do not provide users with a way to resolve.

These changes will allow us to remove the warning from the existing form and provide the ability to directly edit the required values necessary for CPU and Memory utilization.

Breakdown of HPA UX Enhancements

• There are 3 different scenarios to consider,:
  • when a selected workload does not have requests and limits set
  • when a selected workload has request and limits set
  • when there are default values/ranges for requests and limits
• On the HPA form, create sections for CPU and Memory Utilization with a short description.
  • When a user selects "Add CPU Utilization" show CPU Utilization field, CPU requests, CPU limits.
    • Consider how we handle default values/ranges
    • Consider when requests and limits should be editable or just read only
    • Consider how to clearly communicate to users that this is changing their workloads
    • Mark all fields as required
    • Consider supporting percent and value for the utilization field (today we only support percent.
  • When a user selects "Add Memory Utilization" show Memory Utilization field, Memory requests, Memory limits
    • same requirements as above that are listed out for CPU
• Make sure that these changes apply to the create and edit forms both from the HPA list page and from the actions dropdown to applicable workloads.

Assets

• Design Doc (WIP): https://docs.google.com/document/d/1C-wPkuSNrWheIvYvPeB13jfKgGdUem6kLpfSOJMJDQQ/edit
• Marvel (WIP): https://marvelapp.com/prototype/fj6h5eh

Note, 3.x did a lot with this validation.