I recommend using drone/drone-runner-kube:1.0.0-beta.6 which is the latest tagged release. When you use the :latest version of the image you are using an unstable version that may not match the documentation. In this particular instance, the unstable version moves the resource request to the pipeline-level, instead of the step-level.
Curious on the change to have requests at the pipeline level. Is this going to be an option, so we can still define at the step level? Or a change?
I, personally, like the flexibility to define this at the step/container level - we do a good amount of dynamic drone configuration based on repos. We do this via the yaml configuration endpoint. While, not impossible to have this moved to a pipeline level I just like the flexibility.
I recommend reading the full thread to learn more about this history of this change, however, I think the below comment summarizes the problem we were looking to solve:
Also, even if everyone were to add per-container cpu memory/limits we’d still have a bit of “waste” because Kubernetes assumes that a pod’s sum-of cpu/memory settings are required for a node to be able to schedule the pod, while in fact most pipelines are serial so the real capacity needed at any time is simply the most “expensive” container.