{"provider_url":"https://hatena.blog","version":"1.0","title":"How to automatically update Let's Encrypt on Kubernetes (GKE)","image_url":"https://cdn-ak.f.st-hatena.com/images/fotolife/k/kwbtblog/20190606/20190606022931.png","url":"https://www.ekwbtblog.com/entry/2019/01/07/081327","published":"2019-01-07 08:13:27","width":"100%","author_name":"kwbtblog","html":"<iframe src=\"https://hatenablog-parts.com/embed?url=https%3A%2F%2Fwww.ekwbtblog.com%2Fentry%2F2019%2F01%2F07%2F081327\" title=\"How to automatically update Let&#39;s Encrypt on Kubernetes (GKE) - Welcome to new things\" class=\"embed-card embed-blogcard\" scrolling=\"no\" frameborder=\"0\" style=\"display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;\"></iframe>","blog_url":"https://www.ekwbtblog.com/","description":"PS Since the procedure had changed, we have rewritten it in a separate article, along with how to obtain a wildcard certificate. www.ekwbtblog.com Postscript ends here (original article below) It was convenient to use \"cert-manager\" + DNS authentication to automatically update Let's Encrypt on Kuber\u2026","type":"rich","categories":["GCP","GKE","Google Cloud Platform","Kubernetes","Let's Encrypt","cert-manager","k8s"],"height":"190","provider_name":"Hatena Blog","blog_title":"Welcome to new things","author_url":"https://blog.hatena.ne.jp/kwbtblog/"}