a:5:{s:8:"template";s:3333:"
.
{{ links }} ";s:4:"text";s:3901:"Set up Ingress on Minikube with the NGINX Ingress Controller. These parameters can be passed via Helm's --set option $ helm install stable/nginx-ingress --name my-release \\ --set controller.metrics.enabled=true Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. Referencing this secret in an Ingress will tell the Ingress Controller to secure the channel from the client to the loadbalancer using TLS:You can add users to the same file with:On cluster creation the ConfigMap is empty and the above defaults will be applied to the final Ingress Controller deployment.Please do not edit any of the other NGINX ingress related ConfigMaps.If your cluster has TLS enabled, you can terminate TLS either in your application itself by enabling SSL passthrough or let the Ingress Controller terminate for you.Do not copy all the defaults if you do not need to change them, that way we can adjust them in case they need to change.Do make sure you look at the right tag of that repository, when reading this file check that the tagcorresponds to the version of the nginx-ingress-controller-app running on your cluster.The values that you are allowed to configure will depend on the release version of your cluster.As of 9.0.1 and above, you have much more freedom to configure any option available, however keep in mindthat with great power comes great responsibility.Last, we create the Ingress with the according annotations:For terminating TLS in the Ingress Controller you need to first create a TLS secret containing your certificate and private key in the same namespace as the Ingress object:Only the user ConfigMap is safe to edit.Your Giant Swarm installation comes with a default configuration for the Ingress Controller.To use custom values in a specific Ingress add following annotation:For SSL passthrough you need to set an annotation and enable TLS for the host:Depending on the release version of your Tenant Cluster, this ConfigMap is located either in the Tenant Cluster or in the Control Plane.You can route an Ingress to different Services based on the path:You can aggregate several Ingress rules into a single Ingress definition like following: