<p>@euank indicated that it is not required to create a DNS record on GCP in order to make it work.</p>

<p><a href="https://github.com/jetstack/cert-manager/issues/399" rel="nofollow noreferrer">https://github.com/jetstack/cert-manager/issues/399</a></p>

CC BY-SA 3.0
2018-04-27T16:43:15.690Z
2018-04-27T16:43:15.690Z
030
<p>Follow-up to <a href="https://devops.stackexchange.com/q/3609/210">What are trusted providers that offer wildcard certificates and associated costs to be used in an Orchestration Platform like Kubernetes?</a></p>

<p>With <a href="https://github.com/jetstack/cert-manager" rel="nofollow noreferrer">https://github.com/jetstack/cert-manager</a> it would be possible to automatically renew certificates.</p>

<p>At the moment my domain is registered somewhere else than google. Is it required to move the domain to Google DNS in order to use certbot in kubernetes on Google Cloud platform?</p>

<p>At the moment when I add a new subdomain, e.g. abc.somedomain.com I will add a CNAME to my DNS provider. At the moment I have two subdomains and I would like to switch to kubernetes. At the moment the IPs refer to some Virtual Machine instances that reside on another provider.</p>

<p><strong>Current situation</strong></p>

<p>What I understand of Certbot is that it is able to create certificates that are valid for three months. I certbot for almost a year right now and I am happy about it. When I create a new subdomain in my DNS provider I create a CNAME and run certbot and a new certificate is created. This works fine.</p>

<p><strong>Preferred situation</strong></p>

<p>Now I would like to phase out my VM and replace it with kubernetes. I was able to create a kubernetes cluster and expose the microservice to the internet using an ingress. One the IP was exposed, it is possible to access it. </p>

<p><strong>Problems</strong></p>

<p>The problem is that I now would like to get a secure Ingress, i.e. access the microservice via https rather than http, but I am struggling to understand how to configure it in k8s.</p>

<p><strong>Attempt to solve the issue</strong></p>

<ul>
<li>A Google Cloud Platform project has been created</li>
<li>A kubernetes cluster has been created</li>
<li>...</li>
<li>...</li>
<li>...</li>
</ul>

CC BY-SA 3.0
2018-03-16T14:22:30.737Z
Which type of validation does wildcard cert use ? I assume it is DNS, and as such certbot will need a way to create TXT records in the target zone to validate the ownership
Tensibai
CC BY-SA 3.0
2018-03-16T14:39:08.557Z
@Tensibai I have added an extra paragraph that describes where the current DNS records resides and they refer to an IP of a Virtual Machine.
030
<kubernetes><google-cloud-platform><certbot><dns>
Is it required to move a domain to Google DNS in order to use certbot in kubernetes on Google Cloud platform?
030
# Is it required to move a domain to Google DNS in order to use certbot in kubernetes on Google Cloud platform?

(Asked by: username_0 on 2018-03-16)

Follow-up to [What are trusted providers that offer wildcard certificates and associated costs to be used in an Orchestration Platform like Kubernetes?](https://devops.stackexchange.com/q/3609/210)

With <https://github.com/jetstack/cert-manager> it would be possible to automatically renew certificates.

At the moment my domain is registered somewhere else than google. Is it required to move the domain to Google DNS in order to use certbot in kubernetes on Google Cloud platform?

At the moment when I add a new subdomain, e.g. abc.somedomain.com I will add a CNAME to my DNS provider. At the moment I have two subdomains and I would like to switch to kubernetes. At the moment the IPs refer to some Virtual Machine instances that reside on another provider.

**Current situation**

What I understand of Certbot is that it is able to create certificates that are valid for three months. I certbot for almost a year right now and I am happy about it. When I create a new subdomain in my DNS provider I create a CNAME and run certbot and a new certificate is created. This works fine.

**Preferred situation**

Now I would like to phase out my VM and replace it with kubernetes. I was able to create a kubernetes cluster and expose the microservice to the internet using an ingress. One the IP was exposed, it is possible to access it.

**Problems**

The problem is that I now would like to get a secure Ingress, i.e. access the microservice via https rather than http, but I am struggling to understand how to configure it in k8s.

**Attempt to solve the issue**

* A Google Cloud Platform project has been created
* A kubernetes cluster has been created
* ...
* ...
* ...

**Tags:** kubernetes, google-cloud-platform, certbot, dns

> **Comments:**
> **username_1**: Which type of validation does wildcard cert use ? I assume it is DNS, and as such certbot will need a way to create TXT records in the target zone to validate the ownership  
> **username_0**: @username_1 I have added an extra paragraph that describes where the current DNS records resides and they refer to an IP of a Virtual Machine.  

---

## 1 answers

### Answer by username_0 on 2018-04-27. Score: 1 | Accepted answer

@euank indicated that it is not required to create a DNS record on GCP in order to make it work.

<https://github.com/jetstack/cert-manager/issues/399>


---

