Skip to content
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

Automated cherry pick of #8242 to release-3.2 #10559

Conversation

wenjiaswe
Copy link
Contributor

Cherry pick of #8242 on release-3.2.

#8242: embed: configure 'ListenMetricsUrls'

@wenjiaswe
Copy link
Contributor Author

/assign @gyuho

Gyuho, would you please help to review this? xref: #8242 (comment)
One thing that I am not sure about this cherry pick is that in the original PR, there are some code change in etcdmain/grpc_proxy.go, but it looks like those diff are handled by #9894 and not needed in this cherrypick PR. But if I could get your confirmation that would be great!

@wenjiaswe wenjiaswe force-pushed the automated-cherry-pick-of-#8242-upstream-release-3.2 branch from 8d1ca4c to 0de9ea3 Compare March 19, 2019 22:26
@wenjiaswe wenjiaswe requested a review from gyuho March 19, 2019 22:27
@hexfusion
Copy link
Contributor

hexfusion commented Mar 19, 2019 via email

@wenjiaswe wenjiaswe changed the title Automated cherry pick of #8242 Automated cherry pick of #8242 to release-3.2 Mar 19, 2019
@jpbetz
Copy link
Contributor

jpbetz commented Mar 19, 2019

Yes, there exist etcd 3.3.x versions without this fix. So if we add it to 3.2, and someone starts using the flag with etcd 3.2.x and then upgrades to a 3.3.x that does not support the flag, etcd will fail to start. Let's not backport this.

@wenjiaswe
Copy link
Contributor Author

@jpbetz yes, you are right. I will close this.

@wenjiaswe wenjiaswe closed this Mar 19, 2019
@wenjiaswe wenjiaswe deleted the automated-cherry-pick-of-#8242-upstream-release-3.2 branch October 15, 2019 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants