|
1 | 1 | # Node Problem Detector custom scripts |
2 | 2 |
|
3 | | -Adding our own scripts to https://github.com/kubernetes/node-problem-detector and sharing them in case you might find those handy for you use cases. |
| 3 | +Adding our own scripts to https://github.com/kubernetes/node-problem-detector and sharing them in case you might find those handy for your use cases. |
4 | 4 |
|
| 5 | +The script details can be found in `/config/plugin/` but ultimately, they are: |
| 6 | +* `launch-config-drift`: a way to check if your instances launch template has diverged from your ASG launch template |
| 7 | +* `spot-termination`: uses the `meta-data/spot/instance-action` endpoint to check EC2 Spot Instance interruption notice |
| 8 | +* `local-dns-resolver`: checks the response status value received (if any) from the local DNS resolver IP |
| 9 | +* `upstream-dns-resolver`: check if we receive an IPv4 address for a given A record |
| 10 | +* `uptime`: every 5 seconds, checks if the information detailing how long the system has been on since its last restart is acceptable (to us the threshold being 604800 seconds) |
5 | 11 |
|
6 | | -The scripts details can be found in `/config/plugin/` but ultimately, they are: |
7 | | -* `launch-config-drift`: a way to check if your instances launch template has diverged from your asg launch template |
8 | | -* `spot-termination`: uses the `meta-data/spot/instance-action endpoint` to check EC2 Spot Instance interruption notice |
9 | | -* `local-dns-resolver`: checks the response status value received (if any) from the local dns resolver ip |
10 | | -* `upstream-dns-resolver`: check if we receive an IPv4 address for a given A record. |
11 | | -* `uptime`: every 5 seconds, checks if the information detailing how long the system has been on since its last restart is acceptable (to us the threshold being 604800 seconds) |
| 12 | +## Notes |
12 | 13 |
|
| 14 | +*July 2024* - The custom `node problem detector` image is now stored in the `uswitch/node-problem-detector` repository on Quay. |
13 | 15 |
|
14 | | -## Notes |
15 | | -*July 2024 -* The custom `node problem detector` image is now stored in the `uswitch/node-problem-detector` repository on Quay. |
16 | | -<br> |
| 16 | +Base image tags available at: https://explore.ggcr.dev/?repo=registry.k8s.io/node-problem-detector/node-problem-detector |
| 17 | + |
| 18 | +## Releasing a New Version |
| 19 | + |
| 20 | +To publish a new tagged image to Quay, push a semantic version tag to the repository: |
| 21 | + |
| 22 | +```bash |
| 23 | +# Ensure you're on the latest master |
| 24 | +git checkout master |
| 25 | +git pull origin master |
| 26 | + |
| 27 | +# Create and push a tag |
| 28 | +git tag v1.0.0 |
| 29 | +git push origin v1.0.0 |
| 30 | +``` |
| 31 | + |
| 32 | +This triggers the CI workflow which builds and pushes the image to `quay.io/uswitch/node-problem-detector` with both the version tag and the commit SHA. |
0 commit comments