Kubernetes Runner produces error on using limits

Summary

If there are CPU or Memory limits set in the config.toml, the kubernetes runner can not create a pod

Steps to reproduce

Use the following runner config and schedule a build to that runner.

concurrent = 4

[[runners]]
  name = "Kubernetes Runner"
  url = "https://your_gitlab/ci"
  token = "*****"
  executor = "kubernetes"
  [runners.kubernetes]
    namespace = "gitlab-runner"
    privileged = false
    cpus = "100m"
    memory = ""
    service_cpus = ""
    service_memory = ""

Actual behavior

No pod is created. Build stops with a runner error.

Expected behavior

The runner should spawn a pod with ressource limit 100m CPU

Relevant logs and/or screenshots

Error message from Gitlab CI

ERROR: Build failed (system failure): Pod "runner-3a1e75d2-project-344-concurrent-07dumg" is invalid: [spec.containers[0].resources.limits[limits.cpu]: Invalid value: "limits.cpu": must be a standard resource for containers, spec.containers[0].resources.requests[limits.cpu]: Invalid value: "limits.cpu": must be a standard resource for containers]

Environment description

Gitlab CI runner is Docker container gitlab/gitlab-runner:alpine-v1.7.0on selfhosted kubernetes 1.3.

Used GitLab Runner version

bash-4.3# gitlab-runner --version
Version:      1.7.0
Git revision: c66b00d
Git branch:   1-7-stable
GO version:   go1.7.3
Built:        Fri, 21 Oct 2016 21:30:34 +0000
OS/Arch:      linux/amd64

Admin message