Skip to content

tests: construct ResourceClaim differently on v1 #685

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 16, 2025
Merged

tests: construct ResourceClaim differently on v1 #685

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions tests/bats/setup_suite.bash
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,13 @@ validate_prerequisites() {

# Examples: v1, or v1beta1
export TEST_K8S_RESOURCE_API_VERSION

# For resource.k8s.io API versions before v1, a ResourceClaim spec looks
# slightly differently. Use flow-style YAML.
export TEST_DEVCLASSNAME_CD_CHANNEL="exactly: {deviceClassName: compute-domain-default-channel.nvidia.com}"
if [[ "${TEST_K8S_RESOURCE_API_VERSION}" != "v1" ]]; then
export TEST_DEVCLASSNAME_CD_CHANNEL="deviceClassName: compute-domain-default-channel.nvidia.com"
fi
}


Expand Down
6 changes: 4 additions & 2 deletions tests/bats/specs/rc-opaque-cfg-unknown-field.yaml.tmpl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,10 @@ metadata:
spec:
devices:
requests:
- deviceClassName: compute-domain-default-channel.nvidia.com
name: chan
- name: chan
# This part of the ResourceClaim spec changed in
# resource.k8s.io/v1 compared to previous API versions.
${TEST_DEVCLASSNAME_CD_CHANNEL}
config:
- opaque:
driver: compute-domain.nvidia.com
Expand Down