Open slonka opened 2 years ago
Triage: ideally we would like to have more descriptive message with diff and place that is wrong. If we cannot do this in a reasonable time add "troubleshooting" in ProxyTemplate docs.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
@jakubdyszkiewicz how's this in MeshPorxyPatch?
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
I think we should check if it's better with MeshProxyPatch. If it is we should address this in MeshProxyPatch, if it isn't we should just close this issue
Triage: it's the same with MeshProxyPatch
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
@lahabana - as stated by @jakubdyszkiewicz it's the same in MeshProxyPatch - please prioritise this if you still think it's relevant
Hi @slonka,
I'm still using my work-around to cope with https://github.com/kumahq/kuma/issues/4720, which is okay for the time being. For my understanding the adoptions of https://kubernetes.io/docs/concepts/workloads/pods/sidecar-containers/ will fundamentally resolve my issues related the handling of graceful shutdown. I'd rather wait for this than to encourage you spending further effort in resolving the issue within the current setup.
Hi @zd9KgA - I linked to the wrong comment, this issue is unrelated. Yes https://kubernetes.io/docs/concepts/workloads/pods/sidecar-containers/ - will resolve the issues.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
What happened?
Error like this:
Does not help fixing the issue. Maybe this could be improved. The error message seems to come from jsonpb - not sure if we can do anything about this.
Side note: reported via slack.