Skip to content

fix: do not require harp_frp_address for K8s. #34

fix: do not require harp_frp_address for K8s.

fix: do not require harp_frp_address for K8s. #34

Triggered via pull request April 7, 2026 07:48
Status Success
Total duration 6m 24s
Artifacts 3

tests-deploy-k8s.yml

on: pull_request
K8s Deploy Lifecycle (NodePort)
4m 9s
K8s Deploy Lifecycle (NodePort)
K8s-NodePort-Tests-OK
2s
K8s-NodePort-Tests-OK
Fit to window
Zoom out
Zoom in

Annotations

1 warning
K8s Deploy Lifecycle (NodePort)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. 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
k8s_deploy_nodeport_harp.log
17.2 KB
sha256:da9316d33fd4b4b68a631822bad97959a0586c6304140e41b3711305145eb6e4
k8s_deploy_nodeport_nextcloud.log
98.2 KB
sha256:d55b9ab37a59f6129aff8fe33ba6cbcb877fb5cf42b5b2f27cc9c18493b053cd
k8s_deploy_nodeport_resources.txt
389 Bytes
sha256:d64ec79a32ceea90b1f50bc27108991c45173def14f8c82aac027c3d5c4b6b00