Tutorial Agent CI and K8s

Tutorial: Agent CI and Kubernetes

How this agent’s own GitHub Actions workflows, Docker image, and Kubernetes manifests run smoke / post-deploy / nightly jobs.

Deep docs: Tutorial 09 · kubernetes/.

Integrating zyvor-qa into another product’s pipeline? Use Tutorial: External CI/CD instead.

GitHub Actions (agent repo)

Workflows under .github/workflows/ (see also github_integration/workflows/):

Smoke — qa-smoke.yml

Triggers: push/PR to main, nightly ~06:00 UTC, manual dispatch.

• smoke: install + zyvor-qa test (e.g. against https://zyvor.dev), upload reports/ + test-results/
• multi-browser: workflow_dispatch — chromium + firefox + webkit

Post-deploy — qa-post-deploy.yml

Trigger: repository_dispatch type staging-deployed → zyvor-qa run --source github (LLM analysis, regression, optional Slack).

From your product deploy job:

- name: Trigger QA
  run: |
    gh api repos/<owner>/<qa-agent-repo>/dispatches \
      -f event_type=staging-deployed
  env:
    GH_TOKEN: ${{ secrets.QA_DISPATCH_TOKEN }}

Secrets / variables (agent repo)

Kind	Name	Purpose
Variable	ZYVOR_PRODUCT_REPO	Product owner/repo
Variable	ZYVOR_BASE_URL	Deployment under test
Variable	LLM_PROVIDER / LLM_MODEL	Provider selection
Secret	OPENAI_API_KEY / ANTHROPIC_API_KEY	Matching provider
Secret	SLACK_WEBHOOK_URL	Optional notify

Docker

make docker
docker build -f docker/Dockerfile -t zyvor-qa-agent .
docker run --env-file .env zyvor-qa-agent test
docker run --env-file .env -p 8080:8080 zyvor-qa-agent \
  serve --port 8080 --host 0.0.0.0

Published: ghcr.io/hypersdk/zyaiqaagent:v0.4.0 — Deploy and Releases.

Kubernetes

Manifest	Workload
deployment + service + ingress	zyvor-qa serve (+ /health probes)
cronjob	Nightly zyvor-qa test
configmap / secret	Flags, URLs, keys

make k8s-validate
make k8s-apply

One-shot remote: ./scripts/deploy-remote.sh host user --k3s — Deploy and Releases.

Webhook vs Actions

Approach	Best for
zyvor-qa serve + GitHub webhook	Always-on agent; PR comments from live host — GitHub Integration
repository_dispatch into agent Actions	Product deploy triggers agent repo workflow
External Action/container in product CI	Product owns the gate — External CI/CD

Next

Tutorial: External CI/CD · Tutorial: GitHub Integration · Mission Control