The k8s logs command returns "No logs available" or "Pods not running"
when containers aren't ready yet. Since these are non-empty strings,
wait_for_log_output() was treating them as success, causing the
subsequent content check to fail. Also fix unquoted echo glob expansion.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Since --skip-cluster-management is now the default, k8s test scripts
that rely on Kind cluster creation/destruction need explicit flags.
- container-registry: add flag to start/stop/cleanup, add retry loop
for registry catalog check (10 attempts × 3s)
- k8s-deployment-control: add flag to start/stop/cleanup
- database: add flag to first start and final stop, use explicit
--skip-cluster-management for mid-test restart (volume persistence)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Deploy Test / Run deploy test suite (push) Failing after 4sDetails
Webapp Test / Run webapp test suite (push) Failing after 3sDetails
Smoke Test / Run basic test suite (push) Failing after 4sDetails
Publish / Build and publish (push) Failing after 4sDetails
K8s Deployment Control Test / Run deployment control suite on kind/k8s (push) Failing after 3sDetails
Lint Checks / Run linter (push) Failing after 3sDetails
Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/917
Reviewed-by: Thomas E Lackey <telackey@noreply.git.vdb.to>
Co-authored-by: David Boreham <david@bozemanpass.com>
Co-committed-by: David Boreham <david@bozemanpass.com>
Prathamesh Musale
A. F. Dudley
David Boreham