From 10a42a53ec1db1142a92ce95a4f86bb6a7981f99 Mon Sep 17 00:00:00 2001 From: matthias Date: Mon, 10 Mar 2025 23:45:45 +0000 Subject: [PATCH] =?UTF-8?q?kaniko.yaml=20hinzugef=C3=BCgt?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- kaniko.yaml | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 kaniko.yaml diff --git a/kaniko.yaml b/kaniko.yaml new file mode 100644 index 0000000..fa20346 --- /dev/null +++ b/kaniko.yaml @@ -0,0 +1,35 @@ +# This pod specification is intended to be used within the Jenkinsfile for +# building the Docker containers +# +# E.g. /kaniko/executor --context `pwd` --destination localhost:5000/roboto:latest --insecure-registry localhost:5000 --cleanup +--- +kind: Pod +metadata: + name: kaniko +spec: + containers: + - name: jnlp + # Overwriting the jnlp container's default "image" parameter, this will be + # merged automatically with the Kubernetes plugin's built-in jnlp container + # configuration, ensuring that the pod comes up and is accessible + image: 'our-awesome-registry/rtyler/jenkins-agent:latest' + - name: kaniko + image: gcr.io/kaniko-project/executor:debug + imagePullPolicy: Always + # Command and args are important to set in this manner such that the + # Jenkins Pipeline can send commands to be executed from the Jenkinsfile via + # stdin (that's how it really works!) + command: + - /busybox/sh + - "-c" + args: + - /busybox/cat + tty: true + # Kaniko requires a registry, so we're just bringing one online in the pod + # for the intermediate caching of layers + - name: registry + image: 'registry' + command: + - /bin/registry + - serve + - /etc/docker/registry/config.yml