Additionally, the ingress addon can be configured to expose TCP and UDP services by editing the nginx-ingress-tcp-microk8s-conf and nginx-ingress-udp-microk8s-conf ConfigMaps respectively, and then exposing the port in the Ingress controller.
For example, here a Redis service is exposed via TCP:
Yes but this one going to work only if we have single wildcard certificate per cluster, e.g. if I have *.dev.contoso.com indeed I can use it as default one with proposed default-ssl-certificate setting which is awesome and at least solves half of problem
The problem still persists if cluster is serving multiple wildcard domains, e.g. *.dev.contoso.com, *.stage.contoso.com - we can not use any of them as deafult cert
So at moment it seems that the easiest way will be ho have N clusters where N is number of wildcard certificates or hack ingress
[REQUEST] Will you please add the name and namespace of Ingressâs ConfigMap to the document?
I finally found that name nginx-load-balancer-microk8s-conf though. If the name appeared on the document, we wouldnât have to look for the command line options of the controller.
If we change the Ingress to ânetworking.k8s.io/v1â it results in the below error:
kubectl apply -f ingress.yaml
error: error validating âingress.yamlâ: error validating data: [ValidationError(Ingress.spec.rules[0].http.paths[0].backend): unknown field âserviceNameâ in io.k8s.api.networking.v1.IngressBackend, ValidationError(Ingress.spec.rules[0].http.paths[0].backend): unknown field âservicePortâ in io.k8s.api.networking.v1.IngressBackend]; if you choose to ignore these errors, turn validation off with --validate=false
What should the correct documentation for Ingress be referred too??
Hi, currently the nginx ingress doesnât support the v1 networking api.
The networking.k8s.io/v1 has some breaking changes to the manifest. It is not just changing the version. We also need to upgrade the ingress controller.
open source?
Where can I find this code or documentation? Iâm looking the github repo for microk8s and looks to me this consumes the configmap? is this
Since this page states that itâs a nginx ingress, the above seemed appropriate to include in resource definitions. However, the ingress.class of the controller created by this addon is actually public.
Should we add a kubernetes.io/ingress.class: public annotation to the example to clarify this, and document this in the page text?
How can I deploy a second nginx ingress controller to microk8s? I need one controller to serve private intranet traffic and the other to serve public traffic.
is there a reason why the ingressClass name was changed to âpublicâ compared to ânginxâ in the upstream helm chart?
I tried to install the cert-manager and usually thatâs a quick task but due to the me unknown ingressClass name it took hours. Maybe this should be mentioned on the Ingress add-on docs page.
I know about the IngressClass resource, but what I am wondering about is why the name got changed to âpublicâ compared to ânginxâ in the upstream helm chart of the nginx IngressController. It is nowhere mentioned and unfortunately I did not expect it to be changed, so I tried to set up the cert-manager with ânginxâ as the ingessClass name - which of course failed without any error message and so it wasnât trivial for me to fix the issue.