Added protocol documentation
diff --git a/README.md b/README.md
index 80ccdd8..54b820e 100644
--- a/README.md
+++ b/README.md
@@ -34,6 +34,19 @@
To deploy the ccm in the cluster see [deployment.yaml](/deployment.yaml) and configure your cloudstack and api server connection. See the comments.
+### Protocols
+
+This CCM supports TCP, UDP and [TCP-Proxy](https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt)
+LoadBalancer deployments.
+
+For UDP and Proxy Protocol support, CloudStack 4.6 or later is required.
+
+Since kube-proxy does not support the Proxy Protocol or UDP, you should connect this
+directly to containers, for example by deploying a DaemonSet and setting `hostNetwork: true`.
+
+See [service.yaml](/service.yaml) for an example Service deployment and part
+of a suitable configuration for an ingress controller.
+
### Development
Make sure your apiserver is running locally and keep your cloudstack config ready:
diff --git a/service.yaml b/service.yaml
new file mode 100644
index 0000000..0c22df3
--- /dev/null
+++ b/service.yaml
@@ -0,0 +1,30 @@
+---
+kind: Service
+metadata:
+ annotations:
+ service.beta.kubernetes.io/cloudstack-load-balancer-proxy-protocol: enabled
+spec:
+ type: LoadBalancer
+ ports:
+ - name: http-proxy
+ port: 80
+ protocol: TCP
+ targetPort: 80
+ - name: https-proxy
+ port: 443
+ protocol: TCP
+ targetPort: 443
+---
+kind: DaemonSet
+# ...
+spec:
+ template:
+ spec:
+ hostNetwork: true
+ containers:
+ - name: my-ingress-controller
+ ports:
+ - containerPort: 80
+ protocol: TCP
+ - containerPort: 443
+ protocol: TCP
