Skip to content

Fix flyte-core helm charts for multi cluster configuration #5526

Fix flyte-core helm charts for multi cluster configuration

Fix flyte-core helm charts for multi cluster configuration #5526

Re-run triggered September 19, 2023 20:47
Status Success
Total duration 7m 5s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

tests.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
generate_kustomize
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
generate_helm
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
docs
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
compile
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/