# Minimal but meaningful v2.0 GKE configuration

**URL:** <https://community.traefik.io/t/minimal-but-meaningful-v2-0-gke-configuration/1193>\
**Category:** Traefik v2\
**Tags:** kubernetes-crd, kubernetes-ingress\
**Created:** [August 12, 2019, 4:41am UTC](https://community.traefik.io/t/minimal-but-meaningful-v2-0-gke-configuration/1193 "2019-08-12T04:41:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kitanotori](https://sea2.discourse-cdn.com/flex020/user_avatar/community.traefik.io/kitanotori/32/532_2.png) [@Kitanotori](https://community.traefik.io/u/Kitanotori)\
**Post date:** [August 12, 2019, 4:41am UTC](https://community.traefik.io/t/minimal-but-meaningful-v2-0-gke-configuration/1193/1 "2019-08-12T04:41:36Z")

</div>

**Goal**

Get Traefik 2.0 up and running in GKE with minimal but meaningful settings.

**Requirements**

1. Expose Traefik dashboard via domain (e.g. [traefik.yourdomain.com](http://traefik.yourdomain.com))
2. Allow only TLS communication allowed from (who uses plain HTTP nowadays?)
3. Terminate TLS using Traefik with existing wildcard TLS certificate (\*.yourdomain.com)
4. Prefer Kubernetes resource-based configuration over files

**Progress so far**

1. [Custom resources](https://gist.github.com/Kitanotori/5b9cceb89ec4112017659315b646e116)
2. [Service account and related configuration](https://gist.github.com/Kitanotori/eac114f1e9460363e9f58caf7b5100c1)
3. [Deployment](https://gist.github.com/Kitanotori/0b91ea8976ebe341cd0eeb4bf0fecb13)
4. [Services](https://gist.github.com/Kitanotori/45c912bb72c752b9652639de246cdb0c)
5. [Ingress](https://pastebin.com/wXQRX9b5)

Everything works until this point. I have also explained the steps in [this article](https://medium.com/@kita_no_tori/setting-up-a-service-mesh-in-gke-using-linkerd2-and-traefik-2-0-a0518cfc7625).

**Problem**

When I try to add [a second ingress](https://gist.github.com/Kitanotori/58887cf51c33fdacf30dc91831cd1277) in similar fashion, it turns out Traefik doesn't allow me to use the same TLS certificate created as a Secret in different namespace. Is this a bug, or am I forced to put all my ingresses - and consequently my services - in the same namespace in order to be able to use the same wildcard TLS certificate?

I get flooded by this warning:

```auto
Skipping addition of certificate for domain(s) \"*.yourhost.dev,yourhost.dev\", to EntryPoint default, as it already exists for this Entrypoint."

```

Also, I wonder if/how I should set the headers for Linkerd in Traefik 2.0. Example for Traefik 1.x can be found [here](https://linkerd.io/2/tasks/using-ingress/#traefik).