#ingress — Public Fediverse posts

Me voitettiin!!!!!!!
Sammakot lyötiin ylivoimaisesti 176.6 vs 103.4

#ingress
#resistance
#helsinki
#apolloanomaly
#apollo
#anomaly
#ingressAnomaly

Me voitettiin!!!!!!!
Sammakot lyötiin ylivoimaisesti 176.6 vs 103.4

#ingress
#resistance
#helsinki
#apolloanomaly
#apollo
#anomaly
#ingressAnomaly

Done farming. Now at the pre-party.
Tomorrow is the game day.

https://helsinki.blue/

#ingress
#resistance

Viva Las Vegas. #LVR #ExistToResist #PonyRiders #BAF #Ingress

Viva Las Vegas. #LVR #ExistToResist #PonyRiders #BAF #Ingress

#Kubernetes #Ingress und #AWX schadet Ihnen und den Menschen in Ihrer Umgebung 😅 Nach Wochen läuft der Kram endlich über HTTPS. Scheinbar ist es gar nicht so trivial OnPremise Kubernetes mit Ingress laufen zu lassen. Aber die AWX Dokumentation ist da auch gelinde gesagt so gut wie nicht vorhanden (außer, dass vieles depricated ist). Nun ja Ingress muss mit dem Parameter "hostNetwork: true" deployed werden und ohne "ingressClassName: nginx" geht da auch nix...

Package updates for #rke2 including fixes for the #nginx #ingress #vulnerability are on their way to @opensuse #Tumbleweed. This means rke2 as well as the flavors for Kubernetes 1.31, 1.30 and 1.29.

Package updates for #rke2 including fixes for the #nginx #ingress #vulnerability are on their way to @opensuse #Tumbleweed. This means rke2 as well as the flavors for Kubernetes 1.31, 1.30 and 1.29.

wawaweewa #cilium #ingress adventure time!

https://docs.cilium.io/en/stable/network/servicemesh/ingress/
https://docs.cilium.io/en/stable/network/lb-ipam/

look ma! no #MetalLB !

wawaweewa #cilium #ingress adventure time!

https://docs.cilium.io/en/stable/network/servicemesh/ingress/
https://docs.cilium.io/en/stable/network/lb-ipam/

look ma! no #MetalLB !

GREEN TEA (NY) / JUTE / HIGH GROVE / INGRESS / MIOX

Casa Del Popolo, Friday, March 28 at 08:00 PM EDT

Scream & Writhe presents Initial Shock Gig #10

GREEN TEA (NY)
https://newforces.bandcamp.com/album/snowblower
A strong new age harsh noise blend from Nick Forté (guitarist of 90s altered-hardcore band RORSCHACH and blackened-punkers RASPBERRY BULBS).

JUTE
https://jute.bandcamp.com/album/nothing-beats-reality
Local powerhouse.

HIGH GROVE
https://highgrove.bandcamp.com/
Exploratory tape music.

INGRESS
Noisy collaboration between locals FOWL and SPLINTER ASSEMBLY.

MIOX
Fresh on the MTL noise scene after relocating from Halifax. Let's see what they got.

$15
DOORS 8PM
CASA DEL POPOLO

/////

Part of a series of noise shows leading from winter into spring, 2025.

Other events:

Apr. 25 - P'Tit Ours
NYON (NL/QC)
Shadow Pattern (ON)
Zach Rowden (CT)
Skin
Fowl

June 13 - TBA
JHK (NY)
Valise (NY)
VOSP (NY)
+ TBA

As well as Initial Shock III - Jul. 5/6

https://montreal.askapunk.net/event/green-tea-ny-jute-high-grove-ingress-miox

I've successfully migrated my #ESXi #homelab server over to #Proxmox after surprisingly a little bit of (unexpected) trouble - haven't really even moved all of my old services or #Kubernetes cluster back into it, but I'd say the most challenging part I was expecting which is #TrueNAS has not only been migrated, but also upgraded from TrueNAS Core 12 to TrueNAS Scale 24.10 (HUGE jump, I know).

Now then. I'm thinking what's the best way to move forward with this, now that I have 2 separate nodes running Proxmox. There are multiple things to consider. I suppose I could cluster 'em up, so I can manage both of them under one roof but from what I can tell, clustering on Proxmox works the same way as you would with Kubernetes clusters like #RKE2 or #K3s whereby you'd want at least 3 nodes, if not just 1. I can build another server, I have the hardware parts for it, but I don't think I'd want to take up more space I already do and have 3 PCs running 24/7.

I'm also thinking of possibly joining my 2 RKE 2 Clusters (1 on each node) into 1... but I'm not sure how I'd go about it having only 2 physical nodes. Atm, each cluster has 1 Master node and 3 Worker nodes (VMs ofc). Having only 2 physical nodes, I'm not sure how I'd spread the number of master/worker nodes across the 2. Maintaining only 1 (joined) cluster would be helpful though, since it'd solve my current issue of not being able to use one of them to publish services online using #Ingress "effectively", since I could only port forward the standard HTTP/S ports to only a single endpoint (which means the secondary cluster will use a non-standard port instead i.e. 8443).

This turned out pretty long - but yea... any ideas what'd be the "best" way of moving forward if I only plan to retain 2 Proxmox nodes - Proxmox wise, and perhaps even Kubernetes wise?

I've successfully migrated my #ESXi #homelab server over to #Proxmox after surprisingly a little bit of (unexpected) trouble - haven't really even moved all of my old services or #Kubernetes cluster back into it, but I'd say the most challenging part I was expecting which is #TrueNAS has not only been migrated, but also upgraded from TrueNAS Core 12 to TrueNAS Scale 24.10 (HUGE jump, I know).

Now then. I'm thinking what's the best way to move forward with this, now that I have 2 separate nodes running Proxmox. There are multiple things to consider. I suppose I could cluster 'em up, so I can manage both of them under one roof but from what I can tell, clustering on Proxmox works the same way as you would with Kubernetes clusters like #RKE2 or #K3s whereby you'd want at least 3 nodes, if not just 1. I can build another server, I have the hardware parts for it, but I don't think I'd want to take up more space I already do and have 3 PCs running 24/7.

I'm also thinking of possibly joining my 2 RKE 2 Clusters (1 on each node) into 1... but I'm not sure how I'd go about it having only 2 physical nodes. Atm, each cluster has 1 Master node and 3 Worker nodes (VMs ofc). Having only 2 physical nodes, I'm not sure how I'd spread the number of master/worker nodes across the 2. Maintaining only 1 (joined) cluster would be helpful though, since it'd solve my current issue of not being able to use one of them to publish services online using #Ingress "effectively", since I could only port forward the standard HTTP/S ports to only a single endpoint (which means the secondary cluster will use a non-standard port instead i.e. 8443).

This turned out pretty long - but yea... any ideas what'd be the "best" way of moving forward if I only plan to retain 2 Proxmox nodes - Proxmox wise, and perhaps even Kubernetes wise?

Bin bei den neuen "Dispatch" Aufgaben von #Ingress bei Assignment 4/6. Kinetic Capsules hatte ich einige fertig auf Vorrat, Resos und Mods sollte ich heute auf dem Heimweg auch nebenher schaffen. Aber ich geh heute Abend bestimmt nicht noch mal raus zum Felder erstellen - also entweder nur "teil-erledigt" weiter oder morgen den Wecker eine Stunde früher stellen ;)

#IngressPrime #Niantic #Gaming #RunterVomSofa

I've just merged a huge PR to my #Orked (O-tomated RKE Distribution - GREAT NAME I KNOW) that makes it easier than ever for anyone to set up a production-ready #RKE2 #Kubernetes cluster in their #homelab.

With this collection of scripts, all you need to do is just provision the nodes required, including a login/management node, and run the scripts right from the login node to configure all of the other nodes to make up the cluster. This setup includes:

- Configuring the Login node with any required or essential dependencies (such as #Helm, #Docker, #k9s, #kubens, #kubectx, etc.)

- Setup passwordless #SSH access from the Login node to the rest of the Kubernetes nodes

- Update the hosts file for strictly necessary name resolution on the Login node and between the Kubernetes nodes

- Necessary, best practice configurations for all of the Kubernetes nodes including networking configuration, disabling unnecessary services, disabling swap, loading required modules, etc.

- Installation and configuration of RKE2 on all the Kubernetes nodes and joining them together as a cluster

- Installation and configuration of #Longhorn storage, including formatting/configuring their virtual disks on the Worker nodes

- Deployment and configuration of #MetalLB as the cluster's load-balancer

- Deployment and configuration of #Ingress #NGINX as the ingress controller and reverse proxy for the cluster - this helps manage external access to the services in the cluster

- Setup and configuration of #cert-manager to obtain and renew #LetsEncrypt certs automatically - supports both #DNS and HTTP validation with #Cloudflare

- Installation and configuration of #csi-driver-smb which adds support for integrating your external SMB storage to the Kubernetes cluster

Besides these, there are also some other helper scripts to make certain related tasks easy such as a script to set a unique static IP address and hostname, and another to toggle #SELinux enforcement to on or off - should you need to turn it off (temporarily).

If you already have an existing RKE2 cluster, there's a step-by-step guide on how you could use it to easily configure and join additional nodes to your cluster if you're planning on expanding.

Orked currently expects and supports #RockyLinux 8+ (should also support any other #RHEL distros such as #AlmaLinux), but I am planning to improve the project over time by adding more #Linux distros, #IPv6 support, and possibly even #K3s for a more lightweight #RaspberryPi cluster for example.

I've used this exact setup to deploy and manage vital services to hundreds of unique clients/organisations that I've become obsessed with sharing it to everyone and making it easier to get started. If this is something that interests you, feel free to check it out!

If you're wondering what to deploy on a Kubernetes cluster - feel free to also check out my #mika helm chart repo 🥳

🔗 https://github.com/irfanhakim-as/orked

🔗 https://github.com/irfanhakim-as/charts

I've just merged a huge PR to my #Orked (O-tomated RKE Distribution - GREAT NAME I KNOW) that makes it easier than ever for anyone to set up a production-ready #RKE2 #Kubernetes cluster in their #homelab.

With this collection of scripts, all you need to do is just provision the nodes required, including a login/management node, and run the scripts right from the login node to configure all of the other nodes to make up the cluster. This setup includes:

- Configuring the Login node with any required or essential dependencies (such as #Helm, #Docker, #k9s, #kubens, #kubectx, etc.)

- Setup passwordless #SSH access from the Login node to the rest of the Kubernetes nodes

- Update the hosts file for strictly necessary name resolution on the Login node and between the Kubernetes nodes

- Necessary, best practice configurations for all of the Kubernetes nodes including networking configuration, disabling unnecessary services, disabling swap, loading required modules, etc.

- Installation and configuration of RKE2 on all the Kubernetes nodes and joining them together as a cluster

- Installation and configuration of #Longhorn storage, including formatting/configuring their virtual disks on the Worker nodes

- Deployment and configuration of #MetalLB as the cluster's load-balancer

- Deployment and configuration of #Ingress #NGINX as the ingress controller and reverse proxy for the cluster - this helps manage external access to the services in the cluster

- Setup and configuration of #cert-manager to obtain and renew #LetsEncrypt certs automatically - supports both #DNS and HTTP validation with #Cloudflare

- Installation and configuration of #csi-driver-smb which adds support for integrating your external SMB storage to the Kubernetes cluster

Besides these, there are also some other helper scripts to make certain related tasks easy such as a script to set a unique static IP address and hostname, and another to toggle #SELinux enforcement to on or off - should you need to turn it off (temporarily).

If you already have an existing RKE2 cluster, there's a step-by-step guide on how you could use it to easily configure and join additional nodes to your cluster if you're planning on expanding.

Orked currently expects and supports #RockyLinux 8+ (should also support any other #RHEL distros such as #AlmaLinux), but I am planning to improve the project over time by adding more #Linux distros, #IPv6 support, and possibly even #K3s for a more lightweight #RaspberryPi cluster for example.

I've used this exact setup to deploy and manage vital services to hundreds of unique clients/organisations that I've become obsessed with sharing it to everyone and making it easier to get started. If this is something that interests you, feel free to check it out!

If you're wondering what to deploy on a Kubernetes cluster - feel free to also check out my #mika helm chart repo 🥳

🔗 https://github.com/irfanhakim-as/orked

🔗 https://github.com/irfanhakim-as/charts

Update: I've figured out that I've worse networking knowledge than I thought. For people like me that plans to spin up a secondary #Kubernetes cluster - also with #Ingress support to publish your service online, do the following:

1. Ensure #MetalLB and Ingress #NGINX controller have been set up on the cluster, no (port) customisation required - leave them as is

2. Register a domain name on your DNS server i.e. #Cloudflare pointing towards your public IP (router) - I've a #Helm chart that automates this which works with non-enterprise networks with dynamic public IP

3. Set up port forwarding on your router for the second cluster - HTTP (wan port: 8080, virtual host port: 80, lan host IP: Cluster 2 loadbalancer IP) and HTTPS (wan port: 8443, virtual host port: 443, lan host IP: Cluster 2 loadbalancer IP)

4. Deploy an ingress for said service as per usual

All of these steps are the same for your "primary" Cluster except the different WAN ports since 80 and 443 will have been taken by your primary cluster on your router/network.

NOW, the thing I've missed thruout this goose chase, is... when you visit that domain you've specified in your service's ingress (in your Cluster 2), please add the custom port you've used (i.e. :8443) at the back... 🙃 Otherwise, ofc you'll get 404 NGINX errors since when you don't append the custom port at the back of the address, it will reach the default/standard ports 80 (http) or 443 (https) instead.

Jesus, this could've all been avoided if I hadn't went autopilot mode too much in my networking classes years ago. Happy kubernetes-ing everyone.

Update: I've figured out that I've worse networking knowledge than I thought. For people like me that plans to spin up a secondary #Kubernetes cluster - also with #Ingress support to publish your service online, do the following:

1. Ensure #MetalLB and Ingress #NGINX controller have been set up on the cluster, no (port) customisation required - leave them as is

2. Register a domain name on your DNS server i.e. #Cloudflare pointing towards your public IP (router) - I've a #Helm chart that automates this which works with non-enterprise networks with dynamic public IP

3. Set up port forwarding on your router for the second cluster - HTTP (wan port: 8080, virtual host port: 80, lan host IP: Cluster 2 loadbalancer IP) and HTTPS (wan port: 8443, virtual host port: 443, lan host IP: Cluster 2 loadbalancer IP)

4. Deploy an ingress for said service as per usual

All of these steps are the same for your "primary" Cluster except the different WAN ports since 80 and 443 will have been taken by your primary cluster on your router/network.

NOW, the thing I've missed thruout this goose chase, is... when you visit that domain you've specified in your service's ingress (in your Cluster 2), please add the custom port you've used (i.e. :8443) at the back... 🙃 Otherwise, ofc you'll get 404 NGINX errors since when you don't append the custom port at the back of the address, it will reach the default/standard ports 80 (http) or 443 (https) instead.

Jesus, this could've all been avoided if I hadn't went autopilot mode too much in my networking classes years ago. Happy kubernetes-ing everyone.

I've #MetalLB + #NGINX #Ingress controller setup on my #RKE2 #Kubernetes cluster. How it should/would work is for me to:

1. Register a domain name on my DNS server i.e. #Cloudflare pointing towards my public IP (router)

2. Set up port forwarding on my router for HTTP (wan port: 80, virtual host port: 80, lan host IP: my loadbalancer IP) and HTTPS (wan port: 443, virtual host port: 443, lan host IP: my loadbalancer IP)

3. Deploy an ingress for my service

^ this setup works. but right now, I'm in a situation where i want to avoid using WAN ports; 80 and 443 - and possibly switch them with 8080 and 8443. What should I do to be able to do this, because as it is if I do just that, going to the address/domain specified in my service's ingress would return me a 404 NGINX error.

Why I want to do this is because that 80-443 port forwarding rule I've already used for my Cluster 1's loadbalancer IP. I'm now setting things up for my second cluster, Cluster 2, and I can't port forward the same 80-443 pair to Cluster 2's loadbalancer IP.

Please help ;(

I've #MetalLB + #NGINX #Ingress controller setup on my #RKE2 #Kubernetes cluster. How it should/would work is for me to:

1. Register a domain name on my DNS server i.e. #Cloudflare pointing towards my public IP (router)

2. Set up port forwarding on my router for HTTP (wan port: 80, virtual host port: 80, lan host IP: my loadbalancer IP) and HTTPS (wan port: 443, virtual host port: 443, lan host IP: my loadbalancer IP)

3. Deploy an ingress for my service

^ this setup works. but right now, I'm in a situation where i want to avoid using WAN ports; 80 and 443 - and possibly switch them with 8080 and 8443. What should I do to be able to do this, because as it is if I do just that, going to the address/domain specified in my service's ingress would return me a 404 NGINX error.

Why I want to do this is because that 80-443 port forwarding rule I've already used for my Cluster 1's loadbalancer IP. I'm now setting things up for my second cluster, Cluster 2, and I can't port forward the same 80-443 pair to Cluster 2's loadbalancer IP.

Please help ;(

@Priyajsridhar
Best fun day with friends?

Walking around someplace I've never been, outside with mild weather: Boardwalk, Battlefield, Zoo, Sculpture Garden, Arboretum.

Bonus if there are ingress missions to do, too.

Plus there needs to be food and drink after.

#Writephant #funwithfriends #foodanddrink #ingress

@Priyajsridhar
Best fun day with friends?

Walking around someplace I've never been, outside with mild weather: Boardwalk, Battlefield, Zoo, Sculpture Garden, Arboretum.

Bonus if there are ingress missions to do, too.

Plus there needs to be food and drink after.

#Writephant #funwithfriends #foodanddrink #ingress

Bien sur, le souci avec #ingress/ #orna, ce sont les arrêts fréquents :blobcatcoffee:

Bien sur, le souci avec #ingress/ #orna, ce sont les arrêts fréquents :blobcatcoffee:

Bien sur, le souci avec #ingress/ #orna, ce sont les arrêts fréquents :blobcatcoffee:

Bien sur, le souci avec #ingress/ #orna, ce sont les arrêts fréquents :blobcatcoffee:

D'un côté, j'aime beaucoup me ballader -même par temps mauvais, tant que je suis bien couvert- (et jouer à #ingress / #orna , tousse tousse).
De l'autre, et c'est moins drôle... si j'arrête de faire du sport, mon corps va finir par probablement en sucette : diabète, hypertension, problèmes liés au gras et à la prise de poids, etc.

Donc bref, il est grand temps de refaire du vélo. Vu mon peu de résistance face à la bonne bouffe, je ne peux juste pas me permettre d'arrêter.

D'un côté, j'aime beaucoup me ballader -même par temps mauvais, tant que je suis bien couvert- (et jouer à #ingress / #orna , tousse tousse).
De l'autre, et c'est moins drôle... si j'arrête de faire du sport, mon corps va finir par probablement en sucette : diabète, hypertension, problèmes liés au gras et à la prise de poids, etc.

Donc bref, il est grand temps de refaire du vélo. Vu mon peu de résistance face à la bonne bouffe, je ne peux juste pas me permettre d'arrêter.

D'un côté, j'aime beaucoup me ballader -même par temps mauvais, tant que je suis bien couvert- (et jouer à #ingress / #orna , tousse tousse).
De l'autre, et c'est moins drôle... si j'arrête de faire du sport, mon corps va finir par probablement en sucette : diabète, hypertension, problèmes liés au gras et à la prise de poids, etc.

Donc bref, il est grand temps de refaire du vélo. Vu mon peu de résistance face à la bonne bouffe, je ne peux juste pas me permettre d'arrêter.

D'un côté, j'aime beaucoup me ballader -même par temps mauvais, tant que je suis bien couvert- (et jouer à #ingress / #orna , tousse tousse).
De l'autre, et c'est moins drôle... si j'arrête de faire du sport, mon corps va finir par probablement en sucette : diabète, hypertension, problèmes liés au gras et à la prise de poids, etc.

Donc bref, il est grand temps de refaire du vélo. Vu mon peu de résistance face à la bonne bouffe, je ne peux juste pas me permettre d'arrêter.

I've been playing #LocationBasedGames for almost a decade now, starting from #Ingress through most of #Niantic's releases (#PokemonGo, #WizardsUnite, #TransformersHeavyMetal, #PikminBloom) and a few non-Niantic ones (Magic Streets, #JurassicWorldAlive, #TWDOurWorld, #Orna)

I've been playing #LocationBasedGames for almost a decade now, starting from #Ingress through most of #Niantic's releases (#PokemonGo, #WizardsUnite, #TransformersHeavyMetal, #PikminBloom) and a few non-Niantic ones (Magic Streets, #JurassicWorldAlive, #TWDOurWorld, #Orna)

I've been playing #LocationBasedGames for almost a decade now, starting from #Ingress through most of #Niantic's releases (#PokemonGo, #WizardsUnite, #TransformersHeavyMetal, #PikminBloom) and a few non-Niantic ones (Magic Streets, #JurassicWorldAlive, #TWDOurWorld, #Orna)

I've been playing #LocationBasedGames for almost a decade now, starting from #Ingress through most of #Niantic's releases (#PokemonGo, #WizardsUnite, #TransformersHeavyMetal, #PikminBloom) and a few non-Niantic ones (Magic Streets, #JurassicWorldAlive, #TWDOurWorld, #Orna)

I've been playing #LocationBasedGames for almost a decade now, starting from #Ingress through most of #Niantic's releases (#PokemonGo, #WizardsUnite, #TransformersHeavyMetal, #PikminBloom) and a few non-Niantic ones (Magic Streets, #JurassicWorldAlive, #TWDOurWorld, #Orna)

yesterday #resiatance field was this size...
#ingress #mtl

yesterday #resiatance field was this size...
#ingress #mtl

#ingress #brisbane #echo #xma

Fought along with @dino this arvo and it was great fun being at an xma again blobcatdj

#ingress #brisbane #echo #xma

Fought along with @dino this arvo and it was great fun being at an xma again blobcatdj

#ingress #brisbane #echo #xma

Fought along with @dino this arvo and it was great fun being at an xma again blobcatdj

#ingress #brisbane #echo #xma

Fought along with @dino this arvo and it was great fun being at an xma again blobcatdj

#ingress #brisbane #echo #xma

Fought along with @dino this arvo and it was great fun being at an xma again blobcatdj

@artilectzed
to be fair, I have actually seen some of the things I've reported, addressed in a reasonable time frame, at least on #PokémonGO.
#Ingress and #WizardsUnite probably still have quite a lower priority due to (I assume) a smaller active player base.

Anyway, with #BeardGrabber asleep next to his mum in the bedroom, maybe I can get a bit of #dailyExercise as well as a late hack in #Ingress and perhaps hunt for a #Mimikyu costume #Pikachu in #PokémonGO :)
I'll probably also have #HarryPotterWizardsUnite register its 250m walked #dailies, even though I don't really play that game anymore.
I definitely need to fit more exercise into my schedule... Really wish we had an affordable gym nearby, preferably if I could go there together with someone.

@mike I'm about to go out on my #dailyExercise walk while doing my #dailies in #Ingress, #PokemonGo and #HarryPotter #WizardsUnite and get some oil and butter for @Siiw's #SundayDinner plans.
After that I have some laundry to hang up and will see what #BeardGrabber wants me to do with him. :)

If your local #Ingress community is anything like mine, then it's an excellent way to find nearby playgrounds for your #kid. :)

#BeardGrabber and I took a long walk as part of my #DailyExercise and completing my #Ingress, #PokémonGO and #WizardsUnite #dailies.

Still had some unique portals nearby that I hadn't captured and/or hacked, especially for the #MyriadChallenge, and the majority of them were playgrounds. :)

Stopped at some to eat and drink something together. 💜💚

#personal #parenting