{"provider_url":"https://hatena.blog","html":"<iframe src=\"https://hatenablog-parts.com/embed?url=https%3A%2F%2Fwww.mtioutput.com%2Fentry%2F2020%2F07%2F19%2F000000\" title=\"\u3010Kubernetes\u3011\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d7\u30e9\u30b0\u30a4\u30f3\u304c\u5165\u3063\u3066\u3044\u306a\u3044\u3068WorkerNode\u306fNotReady\u3068\u306a\u308b - (O+P)ut\" class=\"embed-card embed-blogcard\" scrolling=\"no\" frameborder=\"0\" style=\"display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;\"></iframe>","description":"\u4e8b\u8c61 Pod\u306e\u30b9\u30c6\u30fc\u30bf\u30b9\u304cPending\u72b6\u614b\u3067kubectl describe pod\u3067\u78ba\u8a8d\u3059\u308b\u3068\u4ee5\u4e0b\u306e\u3088\u3046\u306b\u306a\u3063\u3066\u3044\u308b\u3002 Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 43s (x2 over 43s) default-scheduler 0/2 nodes are available: 1 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate,\u2026","author_url":"https://blog.hatena.ne.jp/mtiit/","height":"190","categories":["DevOps","DevOps-Kubernetes"],"url":"https://www.mtioutput.com/entry/2020/07/19/000000","type":"rich","blog_title":"(O+P)ut","published":"2020-07-19 00:00:00","blog_url":"https://www.mtioutput.com/","title":"\u3010Kubernetes\u3011\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d7\u30e9\u30b0\u30a4\u30f3\u304c\u5165\u3063\u3066\u3044\u306a\u3044\u3068WorkerNode\u306fNotReady\u3068\u306a\u308b","version":"1.0","width":"100%","author_name":"mtiit","image_url":"https://cdn-ak.f.st-hatena.com/images/fotolife/m/mtiit/20191108/20191108224019.jpg","provider_name":"Hatena Blog"}