Open
Conversation
- Pipeline: azure-pipeline-config-tests.yaml (manual trigger) - Shared runner script: run-configtest-scenario.sh (apply → rollout restart → TestKube) - First test scenario: toggle collect_ama_logs_process_metrics, verify telegraf counts - Ginkgo DescribeTable with labeled entries for modular scenario addition - CountProcessInstances() utility function - TestKube CRS files for process-metrics-enabled and process-metrics-default
TestKube clones the repo at the revision specified in the CRS. The configprocessing tests don't exist on ci_prod yet, so the script now patches the CRS revision before applying it.
CountProcessInstances uses bash which doesn't exist in Windows containers. Added CountWindowsProcessInstances using PowerShell's Get-Process, and split the test table so Windows entries use the correct function.
Telegraf is off by default in ama-logs-rs. It only starts when prometheus_data_collection_settings.cluster has urls or kubernetes_services configured.
- Add getFirstRunningPod() to skip errored/terminated pods when counting processes, preventing exec failures on non-running pods - RS expected telegraf count when process-metrics-enabled should be 1 (only procstat), not 2 (main telegraf requires prometheus cluster config)
The operator image (docker.io/kubeshop/testkube-operator) fails to pull on fresh clusters. Instead, extract CRDs from the chart via helm template and apply them before the main install, keeping the operator disabled. This matches existing CI clusters which have CRDs from prior installs.
--show-only doesn't support globs. The CRDs are in a single file: charts/testkube-operator/templates/crds.yaml (gated by installCRD). Also add explicit --set testkube-operator.installCRD=true.
CRDs created via kubectl apply lack Helm metadata labels/annotations. Helm refuses to install if it can't import them into the release. Add app.kubernetes.io/managed-by=Helm label and release annotations to all testkube CRDs after pre-installing them.
Move config test definitions from pipe-delimited workflow strings in the pipeline YAML to a declarative configmap-test-matrix.yaml. A new run-matrix-tests.sh script parses the matrix with yq/jq and runs all cases sequentially. Adding a new scenario is now a single YAML block with no script or pipeline changes needed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.