Cannot modify ingress for arbitrary TCP services per microk8s docs #3025
Comments
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Ping to keep the stale bot away – still awaiting a response. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Hi @jdevries3133, not sure if this is still relevant, sorry for missing this issue (twice) in the past, got here by stale bot as well. This is probably an issue that folks from |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The documentation for microk8s's ingress add-on describes how TCP services can be exposed on arbitrary ports. It shows an example of a Redis service being exposed on port 6739 by a simple changes to the Nginx ingress daemonset.
I am trying to deploy a mail server inside my cluster via the mailu helm chart. It seems like this deployment is up and running fine, I just need to figure out how to expose it.
Minimal Example
I tried to change the ingress daemonset to ask it to listen on port 25 (for starters) by making the following change via
kubectl edit -n ingress daemonset.apps/nginx-ingress-microk8s-controller:- containerPort: 10254 hostPort: 10254 protocol: TCP + - containerPort: 25 + hostPort: 25 + protocol: TCP readinessProbe: failureThreshold: 3 httpGet:After applying this change, the ingress pods restart successfully on two of my three nodes. On one of the three nodes, though, I get the following failure:
Full Example
Later, I added the rest of the mail ports to the daemonset and the tcp-services configmap, so that they look like this:
It does seem like the problem is happening on the same node. It's so weird to me that it's only going wrong on one of the three nodes! Of course, I've checked and double-checked the output of
sudo lsof -i -P -n | grep LISTENon all the hosts to ensure that port 25 is free on all of them.The Plot (my confusion) Thickens
Then again, I just took a look at one of the nodes that was "working." The nginx pod on this host looks happy, it's apparently bound to all the ports I've asked for:
BUT, if I ssh into that node and run my trusty
sudo lsof -i -P -n | grep LISTEN, I don't see any processes bound to those ports! What?!? At this point, you can put my down for thoroughly confused –– my confusion only grows as I continue to draft this issue.For extra context, the mail service looks happy and healthy, though I haven't tested it thoroughly. Here is a birds-eye view of what that looks like. This also shows the
mailu/mailu-frontservice that I'm targeting in the configmap from before:Context
I am running microk8s version 1.23. I have a three-node cluster.
output of
microk8s inspectThe text was updated successfully, but these errors were encountered: