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

[Fix-1983][dinky-gateway] refresh the job manager ip address #1984

Merged
merged 1 commit into from
May 23, 2023

Conversation

andystenhe
Copy link
Contributor

refresh the job manager ip address after the ip address of manager is changed

@andystenhe
Copy link
Contributor Author

with the expose type of k8s is load balance, k8s client fetch the job manger's ip address by using node server ip address(which can not be accessed) at the first time . when the load balance service is ready, k8s client shuld use the service ip adress.

@aiwenmo aiwenmo added the Bug Something isn't working label May 23, 2023
@aiwenmo aiwenmo added this to the 0.8.0 milestone May 23, 2023
Copy link
Contributor

@aiwenmo aiwenmo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@aiwenmo aiwenmo merged commit 1aec0c8 into DataLinkDC:dev May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

[Bug] [k8s app mode] when the expose type of k8s is loadbalance and submit task, a exception will be throw
2 participants