openeew-detection VS gefyra

Q: Are you considering sharing alerts API to use with other systems or generate CAP alerts for public use? A: Here's an open issue with a discussion on CAP support: https://github.com/openeew/openeew-detection/issues/35. Would love to see contributions from the community to move that along! Each country has different ways of alerting its population. We are very aware that not all countries want us to have that access so people can subscribe through the app.

Gefyra attempts to provide the same value as mirrord, but in a different way (via VPN).

Please find the draft here: https://github.com/gefyrahq/gefyra/issues/353

- https://gefyra.dev/

We recently presented our open-source tool Gefyra (https://gefyra.dev) at a "Kubernetes Community Days" event.

My team and I created the open-source tool Gefyra: https://github.com/gefyrahq/gefyra

Gefyra - a tool that creates local infrastructure to write code directly in a Kubernetes cluster while using conventional development tools (including debugger): https://gefyra.dev

As an example: for another project (https://gefyra.dev) I create a Deckfile which contains: - a Keycloak, with initial data (realm, clients, user, etc.) - a service with a sidecar pattern (oauth2-proxy for handling OIDC) - the K8s dashboard for developer experience Have a look: https://github.com/gefyrahq/gefyra-demos/blob/main/deck.yaml And all it takes to run this locally is deck get https://github.com/gefyrahq/gefyra-demos.git Epinio can effectively become part of the Deckfile (so the platform is installed locally already), and the developer can run epinio push immediately after deck get... to bring in new apps. Sounds good.

Mhh. Interesting. With Gefyra (https://gefyra.dev) I automated just that process and it seems to work. I tested it successfully with GKE. However, I decided to use a NodePort service. Is your GCP firewall rule UDP based (TCP is default and does not work)?