![]() Below is the log message from /var/log/message, it can see that this issue is cause by the threshold of ephemeral storage was being hit: All pods goes to “evicted” or “pending” state and require to start all pods manually in order to resume. The cluster somehow evicted my application’s pods due to ephemeral storage. I would like to ask is there any way to avoid this issue or workaround provided by Kubernetes itself? I have set up my private Kubernetes cluster earlier this year, it was stable until a month ago I have encountered the ephemeral storage issue. Cloud being used: (put bare-metal if not on a public cloud) private ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |