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

MasterRole label initialization #987

Closed
johnugeorge opened this issue May 9, 2019 · 4 comments · Fixed by #992
Closed

MasterRole label initialization #987

johnugeorge opened this issue May 9, 2019 · 4 comments · Fixed by #992

Comments

@johnugeorge
Copy link
Member

johnugeorge commented May 9, 2019

@terrytangyuan I see that masterRole re-initialization is removed inside loop in your PR https://github.com/kubeflow/tf-operator/pull/974/files#diff-ec57988f58453ac8c08d62d32e48e0a2L76

If masterRole is not re-initialized inside loop, every pod will have master role to be true once it has got set . What is the reason behind this?

/cc @terrytangyuan

@issue-label-bot
Copy link

Issue Label Bot is not confident enough to auto-label this issue. See dashboard for more details.

@terrytangyuan
Copy link
Member

@johnugeorge I changed it only from a programmatic/lint perspective, the default value for bool is false in Go so masterRole = false isn't really necessary anymore.

@johnugeorge
Copy link
Member Author

@terrytangyuan masterRole = false is inside a loop and masterRole is set only for the pod where it acts as master

@terrytangyuan
Copy link
Member

@johnugeorge Good catch. I am reverting it in #992. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants