From: "Kevin Hilman" <khilman@baylibre.com>
To: kernelci@groups.io, Matthew.Hart@arm.com,
"kernelci@groups.io" <kernelci@groups.io>
Subject: Re: Jenkins example configuration
Date: Mon, 07 Feb 2022 11:31:46 -0800 [thread overview]
Message-ID: <7h5ypqlbh9.fsf@baylibre.com> (raw)
In-Reply-To: <AM5PR0801MB1777F53F11B189594ACC524E9C299@AM5PR0801MB1777.eurprd08.prod.outlook.com>
Hi Matt,
Matthew Hart <Matthew.Hart@arm.com> writes:
> I'm deploying jenkins using the kernelci-jenkins repo and using AWS
> EKS as the kubernetes backend. I can't find any recent examples that
> include the k8s configuration (nodes.yaml i assume)
We have nodes.yaml in the `kernelci-jenkins-data` repo[1], which is
git-crypt protect due to auth tokens etc. associated with the GCE and
Azure k8s clusters.
> so had a few questions:
> * Any complaints if I upstream a patch for adding the AWS cli to the k8s Docker image?
Nope.
> * How is the K8S_CONTEXT environment variable is set in jenkins, to be used in jobs/build.jpl?
The k8s interaction is all done via kubectl, and the host where this
happens has many clusters configured. So all kubectl commands are
called with `kubectl --context ${K8S_CONTEXT}`
> * Is there a record of all the node labels needed to run a full build (monitor, build-trigger, k8s etc
Hmm, not sure if this is documented. Guillaume?
> * Could I get a secrets-redacted example nodes.yaml for casc?
I can't remember if you already have a GPG key for
kernelci-jenkins-data, but if not, either we can set one up, or I can
share one with you privately.
Kevin
[1] https://github.com/kernelci/kernelci-jenkins-data
next prev parent reply other threads:[~2022-02-07 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 20:31 Jenkins example configuration Matthew Hart
2022-02-07 19:31 ` Kevin Hilman [this message]
2022-02-08 12:39 ` Guillaume Tucker
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=7h5ypqlbh9.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=Matthew.Hart@arm.com \
--cc=kernelci@groups.io \
/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