Execute the Pipeline, or stage, inside a pod implemented on a Kubernetes group. The Jenkinsfile must be loaded from either a Multibranch Pipeline or a Pipeline from SCM in order to use this option. The Pod template is defined within the kubernetes <>block. As an example, inside it, you would define it as follows if you want a pod with a Kaniko container:
You shall have to develop a key aws-secret for Kaniko in order to authenticate with ECR. This key should retain the articles.
one other amount is just a ConfigMap that should retain the endpoint of your ECR registry. As an example:
They are an options that are few are placed on a couple of representative implementations. They’re not needed unless clearly stated.
A sequence. The label or label condition on which to run the Pipeline or stage that is individual .
This program is legitimate for node , docker , and dockerfile , and it is needed for node .
A sequence. Run the Pipeline or stage that is individual representative is put on in this customized workplace, as opposed to the standard. It may be either a family member course, in which particular case the customized workplace is going to be beneath the workplace root in the node, or a path that is absolute. For instance:
This program is legitimate for node , docker , and dockerfile .
A boolean, false by default. If real, run the container regarding the node specified during the top-level associated with Pipeline, when you look at the exact same workplace, as opposed to on a unique node completely.
This choice is legitimate for docker and dockerfile , and just has a result when applied to a representative for the specific phase .
A sequence. Runtime arguments to pass through to docker run .
This program is legitimate for docker and dockerfile . Continue reading Pipeline Syntax. Differences when considering top and phase level Agents