Delete EKS Cluster After TTL #366
MohamedMSaeed
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
delete-cluster-after-ttl.yaml
on: schedule
Check-delete-after-for-running-clusters
36s
delete-clusters
4s
deleteClusters-slack-notification
/
slack-notifications
2s
noTTL-slack-notifications
/
slack-notifications
5s
zeroDaysClusters-slack-notifications
/
slack-notifications
4s
threeDaysClusters-slack-notifications
/
slack-notifications
Annotations
1 error and 2 warnings
|
delete-clusters
Process completed with exit code 1.
|
|
Check-delete-after-for-running-clusters
The following actions uses node12 which is deprecated and will be forced to run on node16: aws-actions/configure-aws-credentials@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Check-delete-after-for-running-clusters
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|