[chenwng]

This PR updates kuttl to v0.28.0 and skips limit import test cases with testRunSelector in TestCase.

[mandre]

I wonder if it's possible to make it a bit more dynamic and list boundaries rather than exact version it's supposed to run on (or not run on). This way, all of the testRunSelector can stay untouched on new openstack release, and we would just need to keep the e2e.sh file up to date, once per release cycle. Let me know what you think.

[mandre]

I'd love to have something a bit more dynamic.

What do you think we introduce boundaries, such as we've done in gophercloud?
We could imagine something like:

testRunSelector:
  matchLabels:
    min-2026.1: "true"

Which could be passed from the e2e.sh script with something like:

KNOWN_RELEASES=("2025.1" "2025.2" "2026.1")
labels=""
for release in "${KNOWN_RELEASES[@]}"; do
  if [[ ! "$OS_RELEASE" < "$release" ]]; then
    labels="${labels:+$labels,}min-${release}=true"
  fi
  if [[ ! "$OS_RELEASE" > "$release" ]]; then
    labels="${labels:+$labels,}max-${release}=true"
  fi
done

Where we would only need to update KNOWN_RELEASES when a new test requires new boundaries not yet listed.

[zunken1337]

This overlaps with #208: I have a branch with kuttl v0.28 that adds a 00-test-case.yaml to the 143 tests using openstack-admin, with admin NotIn ["false"] and E2E_KUTTL_SKIP_ADMIN=true passing --test-run-labels admin=false (details in #208 (comment)).

Since a TestCase has a single testRunSelector, the two need to share it. With matchExpressions that works, e.g. a limit test that also needs admin:

testRunSelector:
  matchExpressions:
    - {key: admin, operator: NotIn, values: ["false"]}
    - {key: min-2026.1, operator: In, values: ["true"]}

and e2e.sh builds one --test-run-labels from the release labels plus admin=false when set. I'm happy to rebase #208 on this once it merges.