Ingress for any Kubernetes environment
Last updated
Was this helpful?
Last updated
Was this helpful?
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 , GKE, AWS or Azure; all applications get same endpoints with exactly the same ingress configuration.
Here, we add ingress controller from a 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
Run:
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
Now, edit ingress.yaml with your Host.
Then create Kuard and ingress resource:
See whether ingress is ready
Add ingress controller to your environment. Learn more .
Here, 2p4ptkh9vutgm8tqavigja.webrelay.io is your tunnel endpoint, set it in ingress.yaml
file.
In this example we are using Kuard workload. Deployment file and ingress configuration is available in repository under examples directory. Clone it:
Deployment files for ingress controller and example workload can be found .