Testing a Mozlenium/Synthetics style check locally

Lets assume you have a check you want to run in mozlenium called my-check.js.

git clone https://github.com/mozilla-it/mozlenium
cd mozlenium/checkers/mozlenium
npm i
echo 'async function runner($browser, $driver, $secure) {' > check.js
cat my-check.js >> check.js
echo -e "}\nmodule.exports = runner;" >> check.js

mozafrank / Mozlenium.md

Last active October 14, 2020 16:25

How Mozlenium Works

Tl;dr

Check CRD (k8s) -> Event Stream -> mozlenium Check threads, one thread for each Check -> check threads create k8s jobs to run the check -> check thread polls the job, scrapes status, state, logs, deletes the job, sends state, status, logs to Check CRD

Too long, DID read

When Mozlenium starts the Controller creates all the necessary threads and q ueues.

mozafrank / ExternalSecrets.md

Last active November 12, 2020 18:07

External Secrets in GCP

A Guide to ExternalSecrets

Google Cloud (GCP)

Example Secret:

apiVersion: kubernetes-client.io/v1
kind: ExternalSecret
metadata:
  name: my-k8s-secret

mozafrank / flux.md

Last active July 29, 2020 14:05

How to Flux

How Flux Works

You've got a config repo where you keep your HelmReleases for a given cluster. Flux polls this periodically for manifest changes (based on the git-path you specify) and applies them.
developer adds annotations to HelmRelease to tell flux to watch their upstream docker images.
developer merges code to main in app-specific repo
CI tool builds, tags and pushes image
Flux detects the changed image because of the annotation on the HelmRelease file, triggers an upgrade

mozafrank / data-platform.md

Last active March 10, 2020 14:34

Data Platform Repositories

Adam Frank mozafrank