Skip to content

Add the smoke tests and fix the CI checks#620

Open
rsatal wants to merge 3 commits into
mainfrom
smoke-tests
Open

Add the smoke tests and fix the CI checks#620
rsatal wants to merge 3 commits into
mainfrom
smoke-tests

Conversation

@rsatal

@rsatal rsatal commented May 6, 2026

Copy link
Copy Markdown
Contributor

This PR contains changes for adding the smoke tests and a fix for CI failures

### Smoke tests

  • K6 JavaScript suite covering konk operator + apiserver CRUD flows.
  • Deterministic, parallel-safe: dynamic collision-free resource names, isolated namespaces.
  • Setup → execution → teardown structure; all created resources are cleaned up even on test failure.
  • Auth tokens are fetched at setup and injected per request — no hardcoded credentials, env-var driven.
  • Verbose request/response logging and explicit HTTP status assertions, so failures are diagnosable from CI logs alone.
image

### 2. CI fix — upgrade matrix leg
image

@rsatal

rsatal commented May 6, 2026

Copy link
Copy Markdown
Contributor Author

index.html

@rsatal rsatal force-pushed the smoke-tests branch 2 times, most recently from e007c61 to 7e036c0 Compare May 6, 2026 11:03
Regression introduced by f64afd9. The upgrade matrix leg builds & deploys
konk-operator twice from two different working trees. Two changes from
f64afd9 combined to break it:

  1. GIT_VERSION switched from ?= to :=, so callers can no longer pin it
     across invocations.
  2. New --set=relatedImages.{apiserver,provision,kind}=$(GIT_VERSION)
     overrides flow into the operator-managed runner-konk Helm release
     as overrideValues. With shifting GIT_VERSION the second deploy
     rewrites the release and host-side 'helm test runner-konk' fails
     with 'release: not found'.

Restore ?= for GIT_VERSION; pin it once in the upgrade leg's first
install step and propagate via $GITHUB_ENV. Also run the helm-releases
debug group via infoblox/helm:3 docker image since the GitHub runner
has no helm CLI installed.
@rsatal rsatal changed the title Add the smoke tests Add the smoke tests and fix the CI checks May 6, 2026
@daniel-garcia

Copy link
Copy Markdown
Contributor

Why is k6 being used to test the contract for a custom resource? There are better tools for testing controllers if that is the intent

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants