Remove shell dependency from validator pods #3158
copy-pr-bot[bot]ci.yaml
on: push
variables
/
variables
6s
golang-checks
/
go-check
1m 5s
golang-checks
/
unit tests
34s
golang-checks
/
go-build
1m 48s
config-checks
/
helm-lint
9s
config-checks
/
validate-csv
44s
config-checks
/
validate-helm-values
33s
code-scanning
/
Analyze Go code with CodeQL
4m 28s
coverage
/
coverage
image-builds
/
build-gpu-operator-amd64
image-builds
/
build-gpu-operator-arm64
e2e-tests
/
e2e-tests-containerd
e2e-tests
/
e2e-tests-nvidiadriver
release
/
push-gpu-operator-bundle-image
Annotations
4 errors, 1 warning, and 3 notices
|
golang-checks / go-check
issues found
|
|
golang-checks / go-check:
cmd/rmglob/main.go#L47
G705: XSS via taint analysis (gosec)
|
|
golang-checks / go-check:
cmd/rmglob/main.go#L46
G703: Path traversal via taint analysis (gosec)
|
|
golang-checks / go-check:
cmd/rmglob/main.go#L41
G705: XSS via taint analysis (gosec)
|
|
golang-checks / unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
variables / variables
Operator image: ghcr.io/nvidia/gpu-operator:2e26f568
|
|
variables / variables
Push on build: true
|
|
variables / variables
Commit SHA: 2e26f568
|