-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
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
fix(aws): support for cross-application CLBs with the sql backend #4141
Conversation
if (instances[instanceId] != null) { | ||
String application = instances[instanceId].attributes.get("application") | ||
if (application != null) { | ||
attributes.put("application", application) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This ensures that health objects stored by AmazonLoadBalancerInstanceStateCachingAgent
are indexed by the application of instances the objects relate to, instead of the application of the load balancer itself. This was already done by EddaLoadBalancerCachingAgent
which runs instead of AmazonLoadBalancerInstanceStateCachingAgent
when edda is enabled.
@spinnakerbot cherry-pick 1.17 |
Cherry pick successful: #4142 |
@asher do you think it's possible to cherry pick this in 1.16 as well? Not seeing any breaking changes. Furthermore, I made a custom build where I cherry picked this commit over the |
@spinnakerbot cherry-pick 1.16 |
Cherry pick successful: #4192 |
healthState: Unknown
when SQL is used for clouddriver spinnaker#5061