Merge pull request #326 from hbelmiro/fix-operator-image #5
alyssacgoins
Matrix: build / image-build
Matrix: kfp-kubernetes-native-migration-tests
Annotations
32 warnings
|
build / image-build (viewer-crd-controller, backend/Dockerfile.viewercontroller, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
backend/Dockerfile.viewercontroller#L43
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
backend/Dockerfile.viewercontroller#L41
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
backend/Dockerfile.viewercontroller#L40
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
The 'as' keyword should match the case of the 'from' keyword:
backend/Dockerfile.viewercontroller#L15
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
build / image-build (apiserver, backend/Dockerfile, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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 should be defined before their use:
backend/Dockerfile#L39
UndefinedVar: Usage of undefined variable '$SOURCE_CODE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Variables should be defined before their use:
backend/Dockerfile#L34
UndefinedVar: Usage of undefined variable '$SOURCE_CODE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Variables should be defined before their use:
backend/Dockerfile#L33
UndefinedVar: Usage of undefined variable '$SOURCE_CODE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Variables should be defined before their use:
backend/Dockerfile#L32
UndefinedVar: Usage of undefined variable '$SOURCE_CODE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Variables should be defined before their use:
backend/Dockerfile#L31
UndefinedVar: Usage of undefined variable '$SOURCE_CODE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
build / image-build (cache-deployer, backend/src/cache/deployer/Dockerfile, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
build / image-build (scheduledworkflow, backend/Dockerfile.scheduledworkflow, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
backend/Dockerfile.scheduledworkflow#L74
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
build / image-build (cache-server, backend/Dockerfile.cacheserver, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
The 'as' keyword should match the case of the 'from' keyword:
backend/Dockerfile.cacheserver#L16
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
build / image-build (metadata-envoy, third_party/metadata_envoy/Dockerfile, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
build / image-build (frontend, frontend/Dockerfile, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
Relative workdir without an absolute workdir declared within the build can have unexpected results if the base image changes:
frontend/Dockerfile#L13
WorkdirRelativePath: Relative workdir "./src" can have unexpected results if the base image changes
More info: https://docs.docker.com/go/dockerfile/rule/workdir-relative-path/
|
|
Default value for global ARG results in an empty or invalid base image name:
frontend/Dockerfile#L29
InvalidDefaultArgInFrom: Default value for ARG node:${NODE_VERSION}-${BASE_IMAGE} results in empty or invalid base image name
More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
|
|
Default value for global ARG results in an empty or invalid base image name:
frontend/Dockerfile#L4
InvalidDefaultArgInFrom: Default value for ARG node:${NODE_VERSION}-slim results in empty or invalid base image name
More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
frontend/Dockerfile#L42
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
Legacy key/value format with whitespace separator should not be used:
frontend/Dockerfile#L41
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
build / image-build (launcher, backend/Dockerfile.launcher, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
build / image-build (visualization-server, backend/Dockerfile.visualization, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
Legacy key/value format with whitespace separator should not be used:
backend/Dockerfile.visualization#L37
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
build / image-build (driver, backend/Dockerfile.driver, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
build / image-build (metadata-writer, backend/metadata_writer/Dockerfile, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
backend/metadata_writer/Dockerfile#L6
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
|
build / image-build (persistenceagent, backend/Dockerfile.persistenceagent, .)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
|
|
KFP Kubernetes Native Migration Tests - K8s v1.29.2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@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/
|
|
KFP Kubernetes Native Migration Tests - K8s v1.34.0
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
apiserver
Expired
|
104 MB |
sha256:58ff68c7caa82e0e5ba0bdeafe2d81b606bd8c843eacc197c715d239a07aec7b
|
|
|
cache-deployer
Expired
|
290 MB |
sha256:e0511cfa484ee600eca0dbb61bfebd906d30d6e200aaf2ab3c8568fe791351bf
|
|
|
cache-server
Expired
|
33.4 MB |
sha256:4acf1bc792f64a6a78f42d786ba6c6627a61bf97ea2960ac3e705e96a3eb1ffe
|
|
|
driver
Expired
|
84 MB |
sha256:4b12432a64e58d7f2c30ed9513f436a1fa37b0cd8a73a48c7ab1c0acd176ac88
|
|
|
frontend
Expired
|
166 MB |
sha256:74593b8deb96e421d9aa33dec898fe953ce36f65a4f7f6da1e228d8be6c01a68
|
|
|
kfp-kubernetes-native-migration-tests-artifacts-k8s-v1.29.2
Expired
|
23.2 KB |
sha256:d74974ac3c742c2327a7fe9268d40d2ff2197b87c0b56a5d442312e9dce61ca2
|
|
|
kfp-kubernetes-native-migration-tests-artifacts-k8s-v1.34.0
Expired
|
24.1 KB |
sha256:0cae6faa263e3eba2852d22daebf50e8e023514e89f7dc6d9844de01c7730b77
|
|
|
launcher
Expired
|
129 MB |
sha256:8deb22db966c084d496d020c68ef6f9ff5404ec4c9d6f9735e9a93aad118a261
|
|
|
metadata-envoy
Expired
|
126 MB |
sha256:7593e0caee58632e9f1e990253dbfe57f2e38558fef0012b6bbfa367d344a128
|
|
|
metadata-writer
Expired
|
87 MB |
sha256:a7ae23a3e77a188846d11d4fa18149624de22e4482d9dca9910a8e075b60b1b0
|
|
|
persistenceagent
Expired
|
64.8 MB |
sha256:a11f2a5b14d0398a57d8a7e0fdc8d2c0b38beee6869ff7f3ed8b47df0522d911
|
|
|
scheduledworkflow
Expired
|
77.8 MB |
sha256:cea904ba98572b796b47c571460b7f160d1c7383be1ae405c29ba08629cf3b0a
|
|
|
viewer-crd-controller
Expired
|
22.1 MB |
sha256:3faa9de77508f93a25fdf09eab546bcd4a3c3679480b62a714213a95180b06b2
|
|
|
visualization-server
Expired
|
955 MB |
sha256:358aa05639e5e7b240720f2a86ce95d4bafabf609461417c580596fcf1af404c
|
|