Add the ability to define GPU resource limits on the K8S deploy container step

[mcasperson]

Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your feature request, making sure it's handled appropriately.

Prerequisites

• [ * ] I have searched open and closed issues to make sure it isn't already requested
• [ * ] I have discussed this in #feature-discussion or #backlog and the consensus is that this is something we plan on adding in the near future
• [ * ] I have written a descriptive issue title
• [ * ] I have linked the original source of this feature request
• [ * ] I have tagged the issue appropriately (area/*, kind/enhancement)

The enhancement

What is the problem this solves or benefit it gives

GPU limits can be defined on containers - https://kubernetes.io/docs/tasks/manage-gpus/scheduling-gpus/. The Deploy Kubernetes containers step does not expose the fields required to define these values though. By allowing GPU resource limits to be defined, customers don't have to fall back to the Deploy raw YAML step.

Mockup

Workarounds

The Deploy raw Kubernetes YAML step can be used to deploy containers with GPU limits.

Links

https://secure.helpscout.net/conversation/1238896493/68219/

[mcasperson]

This has been added to 2020.4.0.