Cleanup examples directory

examples/daemonset/haproxy/README.md

@@ -1,67 +0,0 @@
-# Haproxy Ingress DaemonSet
-
-In some cases, the Ingress controller will be required to be run at all the nodes in cluster. Using [DaemonSet](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/apps/daemon.md) can achieve this requirement.
-
-## Prerequisites
-
-If you have another Ingress controller deployed, you will need to make sure your
-Ingress resources target exactly one Ingress controller by specifying the
-[ingress.class](/examples/PREREQUISITES.md#ingress-class) annotation as
-`haproxy`.
-
-This document has also the following prerequisites:
-
-* Create a [TLS secret](/examples/PREREQUISITES.md#tls-certificates) named `tls-secret` to be used as default TLS certificate
-
-Creating the TLS secret:
-
-```console
-$ openssl req \
-  -x509 -newkey rsa:2048 -nodes -days 365 \
-  -keyout tls.key -out tls.crt -subj '/CN=localhost'
-$ kubectl create secret tls tls-secret --cert=tls.crt --key=tls.key
-$ rm -v tls.crt tls.key
-```
-
-## Default Backend
-
-The default backend is a service of handling all url paths and hosts the haproxy controller doesn't understand. Deploy the default-http-backend as follow:
-
-```console
-$ kubectl apply -f ../../deployment/nginx/default-backend.yaml 
-deployment "default-http-backend" configured
-service "default-http-backend" configured
-
-$ kubectl -n kube-system get svc
-NAME                   CLUSTER-IP    EXTERNAL-IP   PORT(S)   AGE
-default-http-backend   192.168.3.4   <none>        80/TCP    30m
-
-$ kubectl -n kube-system get pods
-NAME                                    READY     STATUS    RESTARTS   AGE
-default-http-backend-q5sb6              1/1       Running   0          30m
-```
-
-## RBAC Authorization
-
-Check the [RBAC sample](/examples/rbac/haproxy) if deploying on a cluster with
-[RBAC authorization](https://kubernetes.io/docs/admin/authorization/rbac/).
-
-## Ingress DaemonSet
-
-Deploy the daemonset as follows:
-
-```console
-$ kubectl apply -f haproxy-ingress-daemonset.yaml
-```
-
-Check if the controller was successfully deployed:
-```console
-$ kubectl -n kube-system get ds
-NAME               DESIRED   CURRENT   READY     NODE-SELECTOR   AGE
-haproxy-ingress   2         2         2         <none>          45s
-
-$ kubectl -n kube-system get pods
-NAME                                    READY     STATUS    RESTARTS   AGE
-default-http-backend-q5sb6              1/1       Running   0          45m
-haproxy-ingress-km32x                   1/1       Running   0          1m
-```

examples/daemonset/haproxy/haproxy-ingress-daemonset.yaml

@@ -1,34 +0,0 @@
-apiVersion: extensions/v1beta1
-kind: DaemonSet
-metadata:
-  labels:
-    run: haproxy-ingress
-  name: haproxy-ingress
-spec:
-  template:
-    metadata:
-      labels:
-        run: haproxy-ingress
-    spec:
-      containers:
-      - name: haproxy-ingress
-        image: quay.io/jcmoraisjr/haproxy-ingress
-        args:
-        - --default-backend-service=$(POD_NAMESPACE)/default-http-backend
-        - --default-ssl-certificate=$(POD_NAMESPACE)/tls-secret
-        ports:
-        - name: http
-          containerPort: 80
-        - name: https
-          containerPort: 443
-        - name: stat
-          containerPort: 1936
-        env:
-        - name: POD_NAME
-          valueFrom:
-            fieldRef:
-              fieldPath: metadata.name
-        - name: POD_NAMESPACE
-          valueFrom:
-            fieldRef:
-              fieldPath: metadata.namespace