| commit | 1c21344331d1d42fbdaddf8237501a46727007ab | [log] [tgz] |
|---|---|---|
| author | Joe Gregorio <jcgregorio@google.com> | Thu Jul 28 15:34:36 2022 -0400 |
| committer | SkCQ <skcq-be@skia-corp.google.com.iam.gserviceaccount.com> | Thu Jul 28 20:36:41 2022 +0000 |
| tree | f97f4fcac93a998dd6fbab433b1b78665a535155 | |
| parent | 59b0489a4d464c274e278425ebbda34f8afc5dd4 [diff] |
Add genpromcrd.
A command-line application for producing CRDs for Managed Prometheus.
$ go run ./promk/go/genpromcrd --help
usage: genpromcrd --directory=[k8s-config checkout dir] [options]
options:
-directory string
The directory that contains a checkout of k8s-config.
-dryrun
If true then just print the names of the files that would be written.
-logtostdout
If true then write logging on stdout.
The genpromcrd cmd runs over all Deployments and StatefulSets and
writes out Managed Prometheus CRDs for both scraping and alerting.
For example, given the following file in the git repo that contains
all the cluster config:
k8s-config/
├── monitoring
│ └── appgroups
│ └── perf.yml
└── skia-infra-public
└── perf.yml
All the Rules files for alerts to run for all Deployments and
StatefulSets are held under /monitoring/appgroups and the name
of the file before the '.yml' corresponds to an appgroup label.
Since perf.yaml resides inside a directory associated with a
cluster, the Deployment there runs in the namespace 'somenamespace',
and has .template.label.appgroup=perf, a new file will be written to:
skia-infra-public/perf_somenamespace_appgroup_alerts.yml
which is a modified version of /monitoring/appgroups/perf.yaml, updated
to scrape the deployment in the correct namespace, and it will also
contain 'absent()' alerts for all the alerts defined in 'perf.yml'.
The list of directories processed are defined in:
//kube/clusters/config.json
Bug: skia:13542
Change-Id: If4c1f6b281a236a3613ca4b65c6279d0be90e3d8
Reviewed-on: https://skia-review.googlesource.com/c/buildbot/+/561420
Reviewed-by: Ravi Mistry <rmistry@google.com>
Commit-Queue: Joe Gregorio <jcgregorio@google.com>
This repo contains infrastructure code for Skia.
The main source code repository is a Git repository hosted at https://skia.googlesource.com/buildbot.git. It is possible to check out this repository directly with git clone or via go get.
Using git clone allows you to work in whatever directory you want. You will still need to set GOPATH in order to build some apps (recommended to put this in a cache dir). E.g.:
$ cd ${WORKDIR}
$ git clone https://skia.googlesource.com/buildbot.git
$ export GOPATH=${HOME}/.cache/gopath/$(basename ${WORKDIR})
$ mkdir $GOPATH
$ cd buildbot
Using go get will fetch the repository into your GOPATH directory along with all the Go dependencies. You will need to set GOPATH and GO111MODULE=on. E.g.:
$ export GOPATH=${WORKDIR}
$ export GO111MODULE=on
$ go get -u -t go.skia.org/infra/...
$ cd ${GOPATH}/src/go.skia.org/infra/
Note: go.skia.org is a custom import path and will only work if used like the examples here.
Install Node.js (not as root) and add the bin dir to your path. Optionally run npm install npm -g, as suggested by the npm getting started doc.
Install other dependencies:
$ sudo apt-get install \
jq \
python-django
$ go get -u \
github.com/kisielk/errcheck \
golang.org/x/tools/cmd/goimports \
go.chromium.org/luci/client/cmd/isolate \
go get github.com/mikefarah/yq/v4
Build ~everything:
$ make all
Some code is generated using go generate with external binaries. First, install the version of protoc referenced in the asset creation script and ensure it is on your PATH before other versions of protoc.
Install the necessary go packages:
$ go get -u \ github.com/golang/protobuf/protoc-gen-go \ golang.org/x/tools/cmd/stringer \ google.golang.org/grpc \
To generate code run in this directory:
$ go generate ./...
Install Cloud SDK.
Use this command to run the presubmit tests:
$ ./run_unittests --small