-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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 altstatname for subset clusters #51136
Conversation
Signed-off-by: Rama Chavali <rama.rao@salesforce.com>
/test integ-security-multicluster |
@@ -186,6 +186,11 @@ func (cb *ClusterBuilder) buildSubsetCluster( | |||
return nil | |||
} | |||
|
|||
if len(cb.req.Push.Mesh.OutboundClusterStatName) != 0 { | |||
subsetCluster.cluster.AltStatName = telemetry.BuildStatPrefix(cb.req.Push.Mesh.OutboundClusterStatName, |
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.
why set again as it has been set in buildCluster
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.
We do not have subset name there so SUBSET_NAME wont be replaced
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.
We can get the subset from the clustername.
This way, we do some duplicate work on other fields
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.
You have to parse it for every cluster and get subset name - currently this repetition only happens for subset clusters . IMO this is much faster because subset clusters would be few in number. Unless we change the current signature and pass subset name - we can't avoid this.
Signed-off-by: Rama Chavali <rama.rao@salesforce.com>
In response to a cherrypick label: new pull request created: #51209 |
Regression caused in #46352 . The code has been removed