Skip to content

Node K8s Enablement Canary Testing #3285

Node K8s Enablement Canary Testing

Node K8s Enablement Canary Testing #3285

Triggered via schedule October 16, 2024 20:32
Status Success
Total duration 6m 27s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

node-k8s-canary.yml

on: schedule
k8s  /  ...  /  node-k8s
6m 7s
k8s / node-k8s-attempt-1 / node-k8s
k8s  /  ...  /  node-k8s
k8s / node-k8s-attempt-2 / node-k8s
k8s  /  ...  /  publish-result
5s
k8s / publish-metric-attempt-1 / publish-result
k8s  /  ...  /  publish-result
k8s / publish-metric-attempt-2 / publish-result
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
k8s / node-k8s-attempt-1 / node-k8s
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/aws-secretsmanager-get-secrets@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
k8s / publish-metric-attempt-1 / publish-result
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/aws-secretsmanager-get-secrets@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/