A small tool to view real-world ActivityPub objects as JSON! Enter a URL
or username from Mastodon or a similar service below, and we'll send a
request with
the right
Accept
header
to the server to view the underlying object.
{
"@context": [
"https://join-lemmy.org/context.json",
"https://www.w3.org/ns/activitystreams"
],
"type": "Page",
"id": "https://lemmy.world/post/31091003",
"attributedTo": "https://lemmy.world/u/Hercules",
"to": [
"https://lemmy.world/c/selfhosted",
"https://www.w3.org/ns/activitystreams#Public"
],
"name": "Questions regarding k8s ingress",
"cc": [],
"content": "<p>Hello,</p>\n<p>I have a little homelab that contains a 3 node k3s cluster which im pretty happy about but i got some questions regarding ingress.</p>\n<p>Right now i use nginx as ingress controller and i have the IP of one of the nodes defined under externalIPs. All the nodes are behind the router my ISP gave me so this is nothing special, in this router i configured it to forward port 443 to port 443 of that ip. This all works as excpected im able to access the ingress resources that i want.</p>\n<p>But i wanna make some improvements to this setup and im honestly not really sure how i could implement this.</p>\n<ol>\n<li>Highly available ingress. When the node which contains the IP of the ingress controller goes down im unable to reach my clusters ingress since my router cant forward the traffic. Whats the best way to configure all 3 nodes to be able to receive ingress traffic? (If needed im able to put it behind something like openwrt or opnsense but not sure if this is needed)</li>\n<li>Some ingres resources i only want to expose on my local network. I read online that i can use <code>nginx.ingress.kubernetes.io/whitelist-source-range: 192.168.0.0/24</code> but this doesn’t work i think because since the ingress doesn’t receive the clients actual ip rather it receives an internal k3s ip. Or is their another way to only allow certain ips to access an ingress resource?</li>\n</ol>\n<p>Could someone point my in the right direction for these improvements i wanna make?\nIf you need more information you can always ask!</p>\n<p>Thanks for your time and have a great day!</p>\n",
"mediaType": "text/html",
"source": {
"content": "Hello,\n\nI have a little homelab that contains a 3 node k3s cluster which im pretty happy about but i got some questions regarding ingress.\n\nRight now i use nginx as ingress controller and i have the IP of one of the nodes defined under externalIPs. All the nodes are behind the router my ISP gave me so this is nothing special, in this router i configured it to forward port 443 to port 443 of that ip. This all works as excpected im able to access the ingress resources that i want. \n\nBut i wanna make some improvements to this setup and im honestly not really sure how i could implement this.\n\n1) Highly available ingress. When the node which contains the IP of the ingress controller goes down im unable to reach my clusters ingress since my router cant forward the traffic. Whats the best way to configure all 3 nodes to be able to receive ingress traffic? (If needed im able to put it behind something like openwrt or opnsense but not sure if this is needed)\n2) Some ingres resources i only want to expose on my local network. I read online that i can use `nginx.ingress.kubernetes.io/whitelist-source-range: 192.168.0.0/24` but this doesn't work i think because since the ingress doesn't receive the clients actual ip rather it receives an internal k3s ip. Or is their another way to only allow certain ips to access an ingress resource?\n\nCould someone point my in the right direction for these improvements i wanna make?\nIf you need more information you can always ask!\n\nThanks for your time and have a great day!",
"mediaType": "text/markdown"
},
"attachment": [],
"sensitive": false,
"published": "2025-06-09T16:21:06.146196Z",
"updated": "2025-06-09T16:30:48.676182Z",
"language": {
"identifier": "en",
"name": "English"
},
"audience": "https://lemmy.world/c/selfhosted",
"tag": [
{
"href": "https://lemmy.world/post/31091003",
"name": "#selfhosted",
"type": "Hashtag"
}
]
}