UPDATE: The service is accessible by its domain (#Ingress) as soon as I set the DNS server of my client machine to my PiHole. For other systems not using my local DNS (so outside my network), the domain remains unreachable. My suspicion is an issue with the Port Forwards, but idk what's wrong w em as it is.
Note: this may not be in the exact order. If the order to any of this is important, feel free to point that out.
I've added to #Cloudflare, to my zone (domain), the hostname foo pointing to my network's public IP.
I've deployed everything you'd need including #MetalLB (which determines the dedicated Ingress private IP), #nginx-ingress (type set to LoadBalancer instead of NodePort), and #cert-manager (with both HTTP/DNS clusterissuers). If you want to take a peek at how I've deployed/configured them, more details are on here: https://github.com/irfanhakim-as/orked.
I've added foo.domain to the closest thing resembling to a DNS server that I have, #PiHole, pointing to the dedicated Ingress private IP.
I've set my router's only DNS server to the PiHole's IP.
I've set all my Kubernetes nodes' (Masters and Workers) DNS1 to the Router's IP (DNS2 set to Cloudflare's, 1.1.1.1).
I've created a port forwarding rule for HTTP on my router with 1) WAN Start/End ports set to 80, 2) Virtual Host port set to its nodePort (acquired from kubectl get svc -n ingress-nginx ingress-nginx-controller -o=jsonpath='{.spec.ports[0].nodePort}' i.e. 3XXXX), 3) Protocol set to TCP, and 4) LAN Host address set to the dedicated Ingress private IP.
I've created a port forwarding rule for HTTPS on my router with 1) WAN Start/End ports set to 443, 2) Virtual Host port set to its nodePort (acquired from kubectl get svc -n ingress-nginx ingress-nginx-controller -o=jsonpath='{.spec.ports[1].nodePort}' i.e. 3XXXX), 3) Protocol set to TCP, and 4) LAN Host address set to the dedicated Ingress private IP.
I've deployed a container service, and an Ingress for it, using #LetsEncrypt's DNS validation clusterissuer.
Current result:
Cert-manager creates a certificate automatically and is in a Ready: True state as expected.
The subdomain (foo.domain) however remains unreachable, no 404 errors, no nothing. Just "The connection has timed out" error.
Describing the container service's ingress (foo.domain), shows that it's stuck at "Scheduled for sync".
#Kubernetes and #Networking experts - please tell me what I've done in any of this that were either wrong or unnecessary, or what I'm currently missing here for me to reach my goal of being able to get my container accessible via foo.domain through that Ingress. I suspect that I might be doing something wrong with this whole DNS mess I literally cannot fathom. I feel like I'm insanely close to getting this thing to work, but I fear I'm also insanely close of blowing up my brain.
cc: @telnetlocalhost (thanks for bearing w me and getting me this far)
I honestly have no idea how to get get #ingress working in publishing my services online via #kubernetes in a home setting. I know how I do it at my workplace with my company's cluster, I've no idea how to get it running in mine. I could ask my colleague who's responsible for our company's infra, but that's too mafan than I can handle. They know I'd be too powerful if I can understand networking like I'm not 3 :akko_woozy:
During the time I exhausted myself hustling for the last month or so, I made my autistic store run so efficiently it barely needs me. Still making money.
I did the same thing in my business tavern computer game. I made my tavern run so efficiently it didn’t need me anymore. Made millions in the game and stopped playing it.
Next month I’ll make my 3rd store and that one will be fully automated. Plushie store will pick up eventually.
I have so much time now and I don’t know what to do with it.
Diwrnod cyntaf #DysguCymraeg ar ôl y gwyliau hir, ac am y tro cyntaf ers dyddiau cynnar y Clo, dw i'n dysgu 6 awr y dydd ar Zoom, sy bach o dalcen caled. Ond dau ddosbarth difyr iawn, un yn gorffen y cwrslyfr Mynediad cyn mynd ymlaen at Sylfaen, ar llall yn ddosbarth newydd i fi, yng nghanol y cwrs Uwch.
Mynd i Aberteifi fory am ddosbarth 4 awr wyneb-yn-wyneb, criw sy gyda fi ers 5 mlynedd bellach. Fallai bydd amser chwarae bach o #Ingress os nad ywr tywydd yn rhy wael. Stormydd trwy'r dydd heddi.
Šonedēļ biju uz ģeoeventu, (varētu būt, ka pirmo, kopš kovida?), satiku visādus vecus cilvēkus, un tajā skaitā arī vienu čali ingresa ģemperītī. Parunājāmies, un sagribējās atkal uzspēlēt trīsstūrīšu spēli. Rezultātā suņa pastaigas kļuvušas trīs reizes garākas, paskatīsimies, cik ilgi būs interesanti. #ingress
#IngressPrime
Trying to Smurf my town. It's hard as I feel I'm the only Smurf here 😔 and there's some active red and green players. Which makes it fun, sure! But I'd also love someone to support my work. 😊
I've recently been playing some #IngressPrime when a friend told me I might like it...
I'm still not sure about all of the options on the game. I just got to level 5.
I went with the "blue team" that seems less of a favorite, seeing their numbers. I've been doing my best capturing portals and all that. I dunno if there's any players near me, but I'd love to learn more about the game! 😁
@PlaystationPixy it's a shame that so many people bounce off #Ingress when they start, but I also like that it's a bit “underground” and nerdy, and that everything isn't laid out on a plate for you, and that the game can be played in many different ways.
[Question] Harbor registry with Ingress on a k3d cluster
Hi, Has anyone tried to enable #ingress + #certmanager on a #k3d cluster while installing #harbor registry via #helm ? Any inputs on how to achieve this on macos? TIA
Peth arall sy'n gweithio (i fi) yw mynd amdani gyda'r gêm #Ingress yn lle gemau eraill, sy'n golygu bod rhaid i fi gerdded a/neu mynd ar y beic trydan rhywle bob dydd, os dw i am wneud trionglau mawr gwyrddion dros y wlad.
Es ist wieder Zeit für eine Umfrage! Dieses Mal möchten wir von euch wissen: Welche Plattform nutzt ihr für Gruppenchats?
Falls ihr mehrere Plattformen nutzt, stimmt bitte für die ab, die ihr im Alltag am häufigsten verwendet. Sollte eure liebste Plattform nicht zur Wahl stehen, freuen wir uns über eure Kommentare.
Sobald die Ergebnisse feststehen, werden wir diese in einem Artikel auf GNU/Linux.ch auswerten.