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 13:23
Status Success
Total duration 23m 48s
Artifacts 3
K8s Deploy Lifecycle (LoadBalancer)
4m 35s
K8s Deploy Lifecycle (LoadBalancer)
K8s-LoadBalancer-Tests-OK
3s
K8s-LoadBalancer-Tests-OK
Fit to window
Zoom out
Zoom in

Annotations

1 warning
K8s Deploy Lifecycle (LoadBalancer)
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_loadbalancer_harp.log
17.6 KB
sha256:b88bb2399e74aae20073422c36789cb8bc1a39f567e24387f6aeb282eb1f9250
k8s_deploy_loadbalancer_nextcloud.log
97.2 KB
sha256:355a3e0a9491bb778c3389bd8d6677bfd9c5884acfd86325675d49a195be0c0d
k8s_deploy_loadbalancer_resources.txt
435 Bytes
sha256:781c9dacc3f84e5c810f04e38abe9ec01d1629a5cb44e0f11d5c2be68197afe8