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.

Sign up for GitHub

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

Jump to bottom

Support automatically manage workloads after kmesh rollout #322

Open
hzxuzhonghu opened this issue May 11, 2024 · 2 comments · May be fixed by #417
Open

Support automatically manage workloads after kmesh rollout #322

hzxuzhonghu opened this issue May 11, 2024 · 2 comments · May be fixed by #417
Assignees
@kwb0523 @nlgwcy
Labels
kind/feature
Milestone
v0.4

Comments

@hzxuzhonghu
Copy link
Member

What would you like to be added:

We should not require workloads to be restarted after kmesh restarted. So we may need to auto reload bpf maps after kmesh restarted, but currently some map update depending on kmesh cni.

Why is this needed:

Requiring workloads restart is not acceptable in production
@hzxuzhonghu hzxuzhonghu added this to the v0.4 milestone May 11, 2024
@hzxuzhonghu
Copy link
Member Author

/assign @kwb0523

@hzxuzhonghu
Copy link
Member Author

A little bit further, we may need to pin bpf sys on node, so even during kmesh daemon upgrade, iit wonot influence traffic flowing through kmesh

@nlgwcy nlgwcy self-assigned this Jun 4, 2024
This was referenced Jun 5, 2024
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kwb0523 kwb0523

@nlgwcy nlgwcy

Labels
kind/feature
Projects
None yet
Milestone
v0.4
Development

Successfully merging a pull request may close this issue.

proposal: Reliability of kmesh restart nlgwcy/kmesh
3 participants
@kwb0523 @hzxuzhonghu @nlgwcy