Dne 04. 11. 25 v 5:10 dop. Miroslav Vadkerti napsal(a):
Region: us-east-1
Instances: (name, id, owner)
* N/A (i-09b0e3e626db67deb, AutoScaling)
* N/A (i-058728f094dcbe6a0, AutoScaling)
Unfortunately we are not able to tag these instances with our custom tag, they are automatically created by EKS
autoscaled, would it be possible to update the cleanup script to skip instances which have this tag:
name: k8s.io/cluster-autoscaler/enabled
<http://k8s.io/cluster-autoscaler/enabled>
value: true
Please?
It would not be possible - the goal of this activity is everything correctly
tagged, so we know the owners.
But I can create script that creates these tags for you. With AI it is matter
of 5 minutes. Here it is:
https://github.com/xsuchy/fedora-infra-scripts/blob/main/fix-testing-farm-tags.py
I run it and got this output:
--- Processing Region: us-east-1 ---
[SKIP] Instance i-0b08fcde88335d021 already has 'FedoraGroup' tag.
[SKIP] Instance i-02b5d78e0988e0b65 already has 'FedoraGroup' tag.
[SKIP] Instance i-05cc645e30f76b073 already has 'FedoraGroup' tag.
[SKIP] Instance i-0fe444bb24b282574 already has 'FedoraGroup' tag.
[SKIP] Instance i-0ccea4dfeeaa7f586 already has 'FedoraGroup' tag.
[MATCH] Instance i-09b0e3e626db67deb matches criteria.
-> Found attached volume: vol-0d2ebf64e61481cb0
-> Found attached volume: vol-0e5afcee13a5dc008
[MATCH] Instance i-058728f094dcbe6a0 matches criteria.
-> Found attached volume: vol-0eca7067219163968
-> Found attached volume: vol-0e784aac51b4092a7
[Tagging] 2 Instances in us-east-1 with FedoraGroup=CI.
[SUCCESS] Tagged 2 Instances.
[Tagging] 4 Volumes in us-east-1 with FedoraGroup=CI.
[SUCCESS] Tagged 4 Volumes.
--- Processing Region: us-east-2 ---
[MATCH] Instance i-0d2c4f6e73ac57ba9 matches criteria.
-> Found attached volume: vol-0a64ec59d11adfabd
[MATCH] Instance i-0146c500b191147d4 matches criteria.
-> Found attached volume: vol-04ee4d4cb50abc3d7
[MATCH] Instance i-0289cad4091e56130 matches criteria.
-> Found attached volume: vol-0b0d70edc8f2feef6
-> Found attached volume: vol-0335f8370575aa065
[MATCH] Instance i-08924afeeacbe51d8 matches criteria.
-> Found attached volume: vol-0ce9de7b9290fbdb0
-> Found attached volume: vol-054887c8a75e15e67
-> Found attached volume: vol-03b5293612b58a26b
[MATCH] Instance i-00c0a7359f40d4a18 matches criteria.
-> Found attached volume: vol-0a38a5e250c179160
-> Found attached volume: vol-0c2703c099eae864f
-> Found attached volume: vol-0b01e0523201f239b
[MATCH] Instance i-0f2272384383645e7 matches criteria.
-> Found attached volume: vol-0acceb0702a97c973
-> Found attached volume: vol-0741bd5e5aeeccdb6
-> Found attached volume: vol-0e600163099f56cf3
[MATCH] Instance i-033e7d751d4edbb34 matches criteria.
-> Found attached volume: vol-02a53f055a1320ace
-> Found attached volume: vol-0911a182d6d22ece1
-> Found attached volume: vol-0578469a8c65654bb
[Tagging] 7 Instances in us-east-2 with FedoraGroup=CI.
[SUCCESS] Tagged 7 Instances.
[Tagging] 16 Volumes in us-east-2 with FedoraGroup=CI.
[SUCCESS] Tagged 16 Volumes.
I will run this script for you every month before running my regular report.
--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
--
_______________________________________________
infrastructure mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
