qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Camilla Conte <cconte@redhat.com>
To: qemu-devel@nongnu.org
Cc: berrange@redhat.com, thuth@redhat.com,
	richard.henderson@linaro.org, Camilla Conte <cconte@redhat.com>
Subject: [PATCH v3 5/5] Add Kubernetes runner configuration
Date: Tue, 23 May 2023 13:49:59 +0100	[thread overview]
Message-ID: <20230523124958.27318-1-cconte@redhat.com> (raw)
In-Reply-To: <20230522174153.46801-1-cconte@redhat.com>

Custom values for the gitlab-runner Helm chart.
See https://wiki.qemu.org/Testing/CI/KubernetesRunners.

Signed-off-by: Camilla Conte <cconte@redhat.com>
---
Changes since previous version (PATCH v2 5/5):
- Update ubuntu tag to 22.04. I tested it and it works.
- Remove concurrent jobs limits (use defaults).

 .../ci/gitlab-kubernetes-runners/values.yaml  | 28 +++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100644 scripts/ci/gitlab-kubernetes-runners/values.yaml

diff --git a/scripts/ci/gitlab-kubernetes-runners/values.yaml b/scripts/ci/gitlab-kubernetes-runners/values.yaml
new file mode 100644
index 0000000000..34c9befdce
--- /dev/null
+++ b/scripts/ci/gitlab-kubernetes-runners/values.yaml
@@ -0,0 +1,28 @@
+gitlabUrl: "https://gitlab.com/"
+runnerRegistrationToken: ""
+rbac:
+  create: true
+runners:
+  privileged: true
+  config: |
+    [[runners]]
+      environment = [
+        "DOCKER_HOST=tcp://docker:2376",
+        "DOCKER_TLS_CERTDIR=/certs",
+        "DOCKER_TLS_VERIFY=1",
+        "DOCKER_CERT_PATH=/certs/client"
+      ]
+      [runners.kubernetes]
+        poll_timeout = 1200
+        image = "ubuntu:22.04"
+        cpu_request = "0.5"
+        service_cpu_request = "0.5"
+        helper_cpu_request = "0.25"
+        cpu_request_overwrite_max_allowed = "7"
+        memory_request_overwrite_max_allowed = "30Gi"
+      [[runners.kubernetes.volumes.empty_dir]]
+        name = "docker-certs"
+        mount_path = "/certs/client"
+        medium = "Memory"
+      [runners.kubernetes.node_selector]
+        agentpool = "jobs"
-- 
2.40.1



  parent reply	other threads:[~2023-05-23 13:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 17:41 Add CI configuration for Kubernetes Camilla Conte
2023-05-22 17:41 ` [PATCH v2 1/5] Remove redundant CI variables Camilla Conte
2023-05-23  8:32   ` Daniel P. Berrangé
2023-05-22 17:41 ` [PATCH v2 2/5] Use docker "stable" tag Camilla Conte
2023-05-23  8:33   ` Daniel P. Berrangé
2023-05-30 17:39   ` Daniel P. Berrangé
2023-05-30 17:49     ` Daniel P. Berrangé
2023-05-30 17:53       ` Richard Henderson
2023-05-22 17:41 ` [PATCH v2 3/5] Add loop over docker info Camilla Conte
2023-05-23  8:33   ` Daniel P. Berrangé
2023-05-23 13:06   ` Richard Henderson
2023-05-23 13:26     ` Camilla Conte
2023-05-22 17:41 ` [PATCH v2 4/5] Add CI variable RUNNER_TAG Camilla Conte
2023-05-23  8:34   ` Daniel P. Berrangé
2023-05-22 17:41 ` [PATCH v2 5/5] Add Kubernetes runner configuration Camilla Conte
2023-05-23  8:37   ` Daniel P. Berrangé
2023-05-22 22:52 ` Add CI configuration for Kubernetes Richard Henderson
2023-05-23  7:55   ` Daniel P. Berrangé
2023-05-23  8:24   ` Camilla Conte
2023-05-23 13:07     ` Richard Henderson
2023-05-23 13:28       ` Camilla Conte
2023-05-23 12:49 ` Camilla Conte [this message]
2023-05-24 21:23 ` Richard Henderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230523124958.27318-1-cconte@redhat.com \
    --to=cconte@redhat.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).