Skip to content

fix: do not require harp_frp_address for K8s. #35

fix: do not require harp_frp_address for K8s.

fix: do not require harp_frp_address for K8s. #35

Triggered via pull request April 7, 2026 12:13
Status Success
Total duration 47m 17s
Artifacts 3

tests-deploy-k8s.yml

on: pull_request
K8s Deploy Lifecycle (NodePort)
3m 33s
K8s Deploy Lifecycle (NodePort)
K8s-NodePort-Tests-OK
3s
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
16.9 KB
sha256:15da7f636f78778ef87d57b2db93c805df1a96c50a9d1ebe2a68ad0cd188f0d0
k8s_deploy_nodeport_nextcloud.log
96.7 KB
sha256:8a0407c47d2024bf03686fbb0b8dbc59fb9285da533235b5a5eb559d05ba76db
k8s_deploy_nodeport_resources.txt
389 Bytes
sha256:8719e8fde6abaa33e2777b4504f880f4f699777a0f30f3ce2bd573520edbe28a