Skip to content

UI check to avoid peering a same managed cluster with more than one cluster #5036

UI check to avoid peering a same managed cluster with more than one cluster

UI check to avoid peering a same managed cluster with more than one cluster #5036

Triggered via pull request November 13, 2024 14:20
Status Success
Total duration 11m 9s
Artifacts

frontend-build.yml

on: pull_request
Matrix: resolve-dependencies
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
resolve-dependencies (22)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
resolve-dependencies (20.16.0)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/