yesterday I deployed latest kubernetes-runner with tag latest and we discovered that it’s ignoring resource requests defined in individual steps. This was working on previous stable release 1.0.0-beta.6.
- name: build-dashboard
- make build-dashboard docker=false
But in the kubernetes pod definition there’re only requests defined by drone-runner envs
Could you please look into that?
resource requests are no longer defined for individual steps. See the below thread for the updated syntax as well as the rationale for this change
Similar to Tekton, we could specify resource request as a top-level item and then specify individual container limits as shown below:
+ cpu: 2000
+ memory: 2000MiB
- name: en
- echo hello
- cpu: 2000
- memory: 2000MiB
- name: es
- echo hola
Well in that case, would it be possible to update
drone/cli to support translating resource definition at the pipeline level from jsonnet to YAML?
I compile it with docker image
jsonnet --stream --format=true
This is the jsonnet definition:
event: ['push', 'tag'],
I’d still prefer to use YAML then JSON as output as there’s been some problems with drone processing the JSON format.
The translation from jsonnet to YAML was/is working for resource definition at STEP level but it’s not translating working for resource definition at PIPELINE level.
@bradrydzewski may I bring this back to attention?
This issue was solved with release of Drone/cli version 1.3.1
Now it’s possible to compile Jsonnet definition to YAML with included Kubernetes definitions like Resource requests and limits or nodeSelectors.