Ingress for any Kubernetes environment

Search…
While developing, testing and running workloads it’s always important to have an easy way to access those applications. Every cloud load balancer slightly differs in configuration, pricing and ease of use.
With Web Relay ingress controller it doesn’t matter if your application runs on Minikube, GKE, AWS or Azure; all applications get same endpoints with exactly the same ingress configuration.
Relay Ingress with Kuard
Here, we add ingress controller from a hosted manifest and provide credentials via relay ingress init command. Webhook Relay ingress controller can be found in webrelay-ingress namespace.
To do it on your own, you will need:
Kubernetes environment (in the example above we use Minikube)
Configured kubectl
​Webhook Relay account​
​Add ingress controller to your environment​
Run:
1
relay ingress init
Copied!
This command:
Creates webrelay-ingress namespace
Creates webrelay service account
Creates deployment with the controller
Creates cluster role and binding
Generates access key and secret for the Web Relay server and supplies them as a Kubernetes secret
​Get your tunnel domain name​
1
$ relay tunnel create --group webrelay-ingress hello-ingress
2
2p4ptkh9vutgm8tqavigja.webrelay.io<---->http://127.0.0.1
Copied!
Here, 2p4ptkh9vutgm8tqavigja.webrelay.io is your tunnel endpoint, set it in ingress.yaml file.Add Kuard to your cluster​
In this example we are using Kuard workload. Deployment file and ingress configuration is available in https://github.com/webrelay/ingress repository under examples directory. Clone it:
1
git clone https://github.com/webrelay/ingress
2
cd ingress/examples
Copied!
Now, edit ingress.yaml with your Host.
1
apiVersion: extensions/v1beta1
2
kind: Ingress
3
metadata:
4
  annotations:
5
    kubernetes.io/ingress.class: webrelay    
6
  name: relay-ingress
7
  namespace: default
8
spec:
9
  rules:
10
    - host: 2p4ptkh9vutgm8tqavigmp.webrelay.io # <- set your tunnel host here
11
      http:
12
        paths:
13
        - path: /
14
          backend:
15
            serviceName: kuard
16
            servicePort: 8080
Copied!
Then create Kuard and ingress resource:
1
kubectl create -f kuard.yaml -f ingress.yaml
Copied!
​See whether ingress is ready​
1
relay ingress ls
Copied!
Deployment files for ingress controller and example workload can be found here.
More details on setup and troubleshooting are available on Ingress documentation page.
Examples - Previous
Tunnels
Demoing your website
Last modified 11mo ago
Copy link