mirror of
https://github.com/ansible-collections/kubernetes.core.git
synced 2026-11-21 22:50:20 +00:00
* add matrix to test run helm tests with multiple version
* fix(ci): resolve SonarCloud security findings in helm integration workflow
Enforce HTTPS/TLS for the ansible-core download and pin and wheel-lock the
selinux_please_lie_to_me install. Suppress the two remaining findings
(ansible-core source install and shared test-requirements.txt pins) that
cannot be fixed here without breaking CI, following the existing
sonar.issue.ignore.multicriteria pattern.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* fix(ci): fix remaining sanity and SonarCloud quality gate failures
Remove stale import-3.9!skip entries from tests/sanity/ignore-2.23.txt;
ansible-core devel dropped the import-3.9 sanity test target entirely, so
referencing it now fails the "ignores" sanity test itself.
Switch the e4/e5 sonar.issue.ignore.multicriteria resourceKey patterns in
sonar-project.properties from a bare literal filename to a **/ glob, matching
the working e1-e3 patterns. The literal path was not matching during
analysis, so the two intended suppressions (githubactions:S8541/S8544 on
integration-tests-helm.yaml) never took effect and kept failing the new
code security rating gate.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* test(helm): add regression coverage for plain_http/helm-diff fix, enable helm_uninstall target
helm_diff: replace the unreachable "< 3.13.0" OCI-chart block (plain_http is
only ever true for >= 3.13.0, so the two conditions could never both hold)
with a ">= 3.13.0" case that installs helm-diff and runs a plain_http diff
upgrade, exercising the exact path the plain_http/--plain-http fix touches.
helm_plain_http: replace the HTTPS Bitnami-backed test with one that pushes
a local chart to the plain-HTTP registry from setup_helm_registry and
exercises helm/helm_pull/helm_template against it, so success assertions
verify plain HTTP actually works rather than only that the flag was passed.
Also drop the now-stale redis* .gitignore entry.
helm_uninstall: add the missing aliases file (every sibling helm target has
one; without it the target is not picked up by CI target selection) and
replace a dead assertion gated on helm < 3.7.0 with one that matches the
versions this target actually runs against (>= 3.8.0).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* fix(ci): make the S8541/S8544 SonarCloud suppressions actually take effect
The three flagged lines (ansible-core source install, shared
requirements.txt install) have been open since before the suppression
rules were added, and two prior attempts at the e4/e5 resourceKey pattern
(literal filename, then a **/filename glob) left them unresolved across
multiple fresh analyses - already-raised issues on unchanged lines do not
appear to get re-evaluated against newly added ignore rules.
Broaden e4/e5 to the same .github/workflows/**/*.yaml pattern already
proven to work for e3 (confirmed: githubactions:S7637 has 20 open issues
org-wide but 0 here, despite this repo having @main references e3 is meant
to suppress). This is also a more honest scope: all_green_check.yaml has
the identical ansible-core-from-source and shared-requirements.txt
patterns, not just integration-tests-helm.yaml.
Also make a no-op edit to the two flagged lines (reorder the pip flag and
the two -r files; verified zero package overlap between requirements.txt
and test-requirements.txt) so SonarCloud treats them as changed and
re-evaluates them against the fixed suppression rule, rather than carrying
forward the stale pre-suppression issue state.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* Fix tests and the possibility to run helm tests locally
Fix linters errors
---------
Co-authored-by: GomathiS <gosriniv@redhat.com>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
(cherry picked from commit 782672d2fd)
1.5 KiB
1.5 KiB
Running Helm Integration Tests Locally
This guide explains how to run the helm* integration test targets locally using ansible-test.
Prerequisites
ansible-testavailable in your environment (installed withansible-core)- A Kubernetes cluster accessible via
kubectl(for targets that interact with a cluster)
Configuration
Create an integration_config.yml file under tests/integration/ with the following variables:
setup_helm_version: vx.x.x # e.g v4.2.1
helm_install_path: /path/to/helm/directory
Variables
| Variable | Description |
|---|---|
setup_helm_version |
The Helm version to install (e.g. v4.2.1). The v prefix is optional and will be added automatically if omitted. |
helm_install_path |
Path to a directory that either already contains a helm executable matching the version set in setup_helm_version, or an empty/non-existent directory where Helm will be downloaded and installed. |
If a helm binary already exists at <helm_install_path>/helm, the setup will skip the download and use the existing binary directly.
Running Tests
Run a specific Helm test target with:
ansible-test integration --python <version> -v --no-temp-workdir <target>
For example, to run the helm target with Python 3.12:
ansible-test integration --python 3.12 -v --no-temp-workdir helm
You can run multiple targets in a single command:
ansible-test integration --python 3.12 -v --no-temp-workdir helm helm_diff helm_plugin