From 56e4fe82db27a128b45d926a7922d6cce41c458c Mon Sep 17 00:00:00 2001
From: Christopher Schmidt <fakod666@gmail.com>
Date: Tue, 10 Jul 2018 15:25:48 +0200
Subject: [PATCH] added an Exoscale tutorial

---
 README.md                  |   1 +
 docs/tutorials/exoscale.md | 155 +++++++++++++++++++++++++++++++++++++
 2 files changed, 156 insertions(+)
 create mode 100644 docs/tutorials/exoscale.md

diff --git a/README.md b/README.md
index 304811942..d4f8f7e5d 100644
--- a/README.md
+++ b/README.md
@@ -58,6 +58,7 @@ The following tutorials are provided:
 * Google Container Engine
 	* [Using Google's Default Ingress Controller](docs/tutorials/gke.md)
 	* [Using the Nginx Ingress Controller](docs/tutorials/nginx-ingress.md)
+* [Exoscale](docs/tutorials/exoscale.md)
 
 ## Running Locally
 
diff --git a/docs/tutorials/exoscale.md b/docs/tutorials/exoscale.md
new file mode 100644
index 000000000..bab9c9e5a
--- /dev/null
+++ b/docs/tutorials/exoscale.md
@@ -0,0 +1,155 @@
+# Setting up ExternalDNS for Exoscale
+
+## Prerequisites
+
+Exoscale provider support was added via [this PR](https://github.com/kubernetes-incubator/external-dns/pull/625), thus you need to use external-dns with this PR merged.
+
+The Exoscale provider expects that your Exoscale zones, you wish to add records to, already exists
+and are configured correctly. It does not add, remove or configure new zones in anyway.
+
+To do this pease refer to the [Exoscale DNS documentation](https://community.exoscale.com/documentation/dns/).
+
+Additionally you will have to provide the Exoscale...:
+
+* API Key
+* API Secret
+* API Endpoint
+* Elastic IP address, to access the workers
+
+## Deployment
+
+Deploying external DNS for Exoscale is actually nearly identical to deploying
+it for other providers. This is what a sample `deployment.yaml` looks like:
+
+```yaml
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  name: external-dns
+spec:
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      labels:
+        app: external-dns
+    spec:
+      # Only use if you're also using RBAC
+      # serviceAccountName: external-dns
+      containers:
+      - name: external-dns
+        image: registry.opensource.zalan.do/teapot/external-dns
+        args:
+        - --source=ingress # or service or both
+        - --provider=exoscale
+        - --domain-filter={{ my-domain }}
+        - --policy=sync # if you want DNS entries to get deleted as well
+        - --txt-owner-id={{ owner-id-for-this-external-dns }}
+        - --exoscale-endpoint={{ endpoint }} # usually https://api.exoscale.ch/dns
+        - --exoscale-apikey={{ api-key}}
+        - --exoscale-apisecret={{ api-secret }}
+```
+
+## RBAC
+
+If your cluster is RBAC enabled, you also need to setup the following, before you can run external-dns:
+
+```yaml
+apiVersion: v1
+kind: ServiceAccount
+metadata:
+  name: external-dns
+  namespace: default
+
+---
+
+apiVersion: rbac.authorization.k8s.io/v1beta1
+kind: ClusterRole
+metadata:
+  name: external-dns
+rules:
+- apiGroups: [""]
+  resources: ["services"]
+  verbs: ["get","watch","list"]
+- apiGroups: [""]
+  resources: ["pods"]
+  verbs: ["get","watch","list"]
+- apiGroups: ["extensions"]
+  resources: ["ingresses"]
+  verbs: ["get","watch","list"]
+
+---
+
+apiVersion: rbac.authorization.k8s.io/v1beta1
+kind: ClusterRoleBinding
+metadata:
+  name: external-dns-viewer
+roleRef:
+  apiGroup: rbac.authorization.k8s.io
+  kind: ClusterRole
+  name: external-dns
+subjects:
+- kind: ServiceAccount
+  name: external-dns
+  namespace: default
+```
+
+## Testing and Verification
+
+**Important!**: Remember to change `example.com` with your own domain throughout the following text.
+
+Spin up a simple nginx HTTP server with the following spec (`kubectl apply -f`):
+
+```yaml
+apiVersion: extensions/v1beta1
+kind: Ingress
+metadata:
+  name: nginx
+  annotations:
+    kubernetes.io/ingress.class: nginx
+    external-dns.alpha.kubernetes.io/target: {{ Elastic-IP-address }}
+spec:
+  rules:
+  - host: via-ingress.example.com
+    http:
+      paths:
+      - backend:
+          serviceName: nginx
+          servicePort: 80
+
+---
+
+apiVersion: v1
+kind: Service
+metadata:
+  name: nginx
+spec:
+  ports:
+  - port: 80
+    targetPort: 80
+  selector:
+    app: nginx
+
+---
+
+apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+  name: nginx
+spec:
+  template:
+    metadata:
+      labels:
+        app: nginx
+    spec:
+      containers:
+      - image: nginx
+        name: nginx
+        ports:
+        - containerPort: 80
+```
+
+**Important!**: Don't run dig, nslookup or similar immediately (until you've
+confirmed the record exists). You'll get hit by [negative DNS caching](https://tools.ietf.org/html/rfc2308), which is hard to flush.
+
+Wait about 30s-1m (interval for external-dns to kick in), then check Exoscales [portal](https://portal.exoscale.com/dns/example.com)... via-ingress.example.com should appear as a A and TXT record with your Elastic-IP-address.
\ No newline at end of file