fix: do not require harp_frp_address for K8s. #3297
tests-deploy.yml
on: pull_request
NC In Host
2m 29s
NC In Julius Docker
1m 8s
NC In Julius Docker(DSP-HTTP)
1m 57s
NC In Julius Docker(DSP-HTTPS)
1m 22s
NC In Host(Redis)
2m 29s
NC In Host(network=host)
2m 1s
NC In Julius Docker (HaRP-Bridge network)
1m 9s
NC In Julius Docker (HaRP-Bridge network-no FRP TLS)
1m 9s
NC In Host (HaRP-Host network)
2m 5s
NC In Host (Manual HaRP-Host network)
7m 6s
NC In Julius Docker(DSP-HTTPS-BRIDGE)
1m 23s
NC In Host(Redis) Deploy options
2m 25s
Tests-Deploy-OK
4s
Annotations
6 warnings
|
NC In Host(Redis)
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/
|
|
NC In Host(network=host)
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/
|
|
NC In Host (HaRP-Host network)
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/
|
|
NC In Host(Redis) Deploy options
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/
|
|
NC In Host
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/
|
|
NC In Host (Manual HaRP-Host network)
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 | |
|---|---|---|---|
|
dsp_http_container.json
|
3.26 KB |
sha256:e48fc4ac7390a13e0b60e6ff2ece58fa906bc13f74d04af54165ca764097d666
|
|
|
dsp_http_container.log
|
937 Bytes |
sha256:53663068a6770d87aef9d0dd5f8ac8c40b8b1f77c024454115184f479e491348
|
|
|
dsp_http_nextcloud.log
|
592 Bytes |
sha256:2d288f30ebb44d5816be4e4789f3cb92aebb4029f79d38bfbd71ed1fd30581db
|
|
|
dsp_https_bridge_container.json
|
3.39 KB |
sha256:abe58897546d98e65098cbe5e0a57014b972f57fd159871f3ad9fdc2a672f8da
|
|
|
dsp_https_bridge_container.log
|
891 Bytes |
sha256:c3ca032cdf09f682d7077ddafa8bf6060fd6bd745f06f62e965b1948ee6e3b34
|
|
|
dsp_https_bridge_haproxy.log
|
3.69 KB |
sha256:311ae6a9d8878db492ffd6c1b84774654ea6cc5800c7f8e30216f06025f5c315
|
|
|
dsp_https_bridge_nextcloud.log
|
1.42 KB |
sha256:05a2b0c9dd69961865d8a66ee89b8408d4aa2ed984471c8727a63e7fc54ae9f7
|
|
|
dsp_https_container.json
|
3.28 KB |
sha256:aa1bc08266a1308a13ff19724475a6bc82556b19d8ea5f0d3300f89136566d33
|
|
|
dsp_https_container.log
|
884 Bytes |
sha256:69b52ebb9938f99e81eea205799068dc3612766910c1b95ee4152932e5e28660
|
|
|
dsp_https_haproxy.log
|
3.66 KB |
sha256:6d4c6ee8a38acd2ee6321f89b69d02fe694fc001023305d347f3b8e828cdd0db
|
|
|
dsp_https_nextcloud.log
|
1.42 KB |
sha256:25f8122d0af07217f698609042f98fbd6308f850b60fcd6039a04209dff97eef
|
|
|
nc_docker_app_docker_container.json
|
147 Bytes |
sha256:1e2f88c03017a035bdaf4c027a24d47af6fdc0250c8f5f06610379341eb62f34
|
|
|
nc_docker_app_docker_container.log
|
935 Bytes |
sha256:ff75c5bcc507c066bd399a72e464059b4160ac07bea3a2974e732b52ac3800a9
|
|
|
nc_docker_app_docker_nextcloud.log
|
601 Bytes |
sha256:c4741c5cbd089e46fbb958041622caaa8882bf42e6272c186391c133cba58ff7
|
|
|
nc_host_app_docker_container.json
|
3.2 KB |
sha256:799d83f104f93f3f1084f80341883c5155dbf7815d4ccd45cbea3575d42517d6
|
|
|
nc_host_app_docker_container.log
|
938 Bytes |
sha256:c6d6a17844a7a8583ec18cc32056d39a52d3456ba6ffd68c809a8c6f4a23169c
|
|
|
nc_host_app_docker_nextcloud.log
|
52.6 KB |
sha256:0a510ea1861995dec2c9f64bb9088cc12ed50ce0aebde915c2f02db88f014d2a
|
|
|
nc_host_app_docker_redis_container.json
|
3.23 KB |
sha256:4c99b11940e3ba0bc158ee8b53d32c3a4c7f512f0565d6bdf8774d9670eed508
|
|
|
nc_host_app_docker_redis_container.log
|
938 Bytes |
sha256:82bce9e88f49066a3bcbce0f57f55a743540ff4e0bf5f1decff68ac6f55bbb32
|
|
|
nc_host_app_docker_redis_deploy_options_container.json
|
3.3 KB |
sha256:f67de633a7baa7630d3933e9dd3c2880d9ba22ca878bb1ffac7e2d52c70b40e7
|
|
|
nc_host_app_docker_redis_deploy_options_container.log
|
940 Bytes |
sha256:28e78250fcae7dbf5ca22fe30b32a3bfae63d6ae0ef7e31b11c655d1cce22e37
|
|
|
nc_host_app_docker_redis_deploy_options_nextcloud.log
|
53.1 KB |
sha256:e2a5fa26f9cf721db28af0cdbb6ff24fe90e61780c88a99d3f0b4d22628ad1e4
|
|
|
nc_host_app_docker_redis_nextcloud.log
|
52.5 KB |
sha256:eeaba775c7eee40a274dbea162c6c65ca3a9d43ac9240763022445af7bd8daef
|
|
|
nc_host_network_host_container.json
|
3.23 KB |
sha256:13f42cb7ac722a7aa6e363079cfe2a832fdff4b3c2c8e51c9b49a4ba90ef3887
|
|
|
nc_host_network_host_container.log
|
937 Bytes |
sha256:759b25cbdc4702f997e4442f5283f60b7ba0485202bb58b21890dc3bd479b24e
|
|
|
nc_host_network_host_nextcloud.log
|
54.1 KB |
sha256:5e24c1a54ce2d3fe090c12970b91155182ad139eb9d17c622879c5dc307c7962
|
|