We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently clustercron only matches instance id's.
It would be very useful if it could also match the eth0 ip with the registered ALB IP targets.
So;
Clustercron should collect it own instance id and ip4 on eth0.
When
aws elbv2 describe-target-groups --name targetgroup
shows
"TargetType": "instance"
the current instance id matching can take place
{ "TargetHealthDescriptions": [ { "Target": { "Id": "i-0184d05d7bf532e14",
when it shows
"TargetType": "ip"
it should match with the healthy ip target that matches.
aws elbv2 describe-target-health --target-group-arn arn
{ "TargetHealthDescriptions": [ { "Target": { "Id": "172.31.8.112",
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently clustercron only matches instance id's.
It would be very useful if it could also match the eth0 ip with the registered ALB IP targets.
So;
Clustercron should collect it own instance id and ip4 on eth0.
When
aws elbv2 describe-target-groups --name targetgroup
shows
"TargetType": "instance"
the current instance id matching can take place
when it shows
"TargetType": "ip"
it should match with the healthy ip target that matches.
aws elbv2 describe-target-health --target-group-arn arn
The text was updated successfully, but these errors were encountered: