<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<oembed>
  <author_name>kwbtblog</author_name>
  <author_url>https://blog.hatena.ne.jp/kwbtblog/</author_url>
  <blog_title>Welcome to new things</blog_title>
  <blog_url>https://www.ekwbtblog.com/</blog_url>
  <categories>
    <anon>Docker</anon>
    <anon>GCP</anon>
    <anon>GKE</anon>
    <anon>Google Cloud Platform</anon>
    <anon>HTTPS</anon>
    <anon>Kubernetes</anon>
    <anon>Let's Encrypt</anon>
    <anon>k8s</anon>
  </categories>
  <description>It was convenient to use &quot;cert-manager&quot; + DNS authentication to automatically update Let's Encrypt on Kubernetes (GKE) without processing on the service side. I wrote Introductory note before, but the procedure had changed, so I rewrote it with how to get a wildcard certificate. Based on the officia…</description>
  <height>190</height>
  <html>&lt;iframe src=&quot;https://hatenablog-parts.com/embed?url=https%3A%2F%2Fwww.ekwbtblog.com%2Fentry%2F2019%2F06%2F06%2F025419&quot; title=&quot;How to automatically renew Let&amp;#39;s Encrypt on Kubernetes (GKE) (wildcard certificate) - Welcome to new things&quot; class=&quot;embed-card embed-blogcard&quot; scrolling=&quot;no&quot; frameborder=&quot;0&quot; style=&quot;display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;&quot;&gt;&lt;/iframe&gt;</html>
  <image_url>https://cdn-ak.f.st-hatena.com/images/fotolife/k/kwbtblog/20190606/20190606022931.png</image_url>
  <provider_name>Hatena Blog</provider_name>
  <provider_url>https://hatena.blog</provider_url>
  <published>2019-06-06 02:54:19</published>
  <title>How to automatically renew Let's Encrypt on Kubernetes (GKE) (wildcard certificate)</title>
  <type>rich</type>
  <url>https://www.ekwbtblog.com/entry/2019/06/06/025419</url>
  <version>1.0</version>
  <width>100%</width>
</oembed>
