It seems newer versions fixed a leak. Don't know which component is that is leaking for you, though.
But, for example, this is one that have been fixed in a newer version: https://github.com/kubernetes/kubernetes/pull/65339 See the changelog here for all 1.10.x minors: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.10.md If anything seems like your case, I'd try upgrading. But please let us know if it's fixed in released versions or not yet :-) On Friday, September 14, 2018, Yakov Sobolev <ysobo...@ashland.edu> wrote: > We are running Kubernetes 1.10.2 and we noticed memory leak on the master > node. It is known issue? What is the remedy? > We are running several clusters on VMs and confirmed memory leak on all of > them. Only out-of-the box components are running on master nodes. > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
