Currently, the the value for the field `.containers.cpus` is ignored when creating a new pod, the default of "one" being used, instead.
To reproduce, post ucr-registry-cert.json to the pods API:
Then, look at the CPUs value for the second container. Compare with the value from the original.
I have confirmed that the fields "mem", and "disk" are in fact respected, but "cpus" is indeed ignored (for the second container resources specification) click save click save.
When using dcos marathon pod add ucr-registry-cert.json, where the push-image container uses 0.01 CPU, the resulting pod definition on DC/OS shows 1 CPU: