How to Deploy Ngrok Ingress Controller on Kubernetes Without a LoadBalancer

·3 views

The Ngrok Ingress Controller lets developers expose Kubernetes applications to the internet by routing traffic through Ngrok's edge, eliminating the need for a traditional LoadBalancer service. It handles traffic management, TLS, load balancing, and authentication at the Ngrok edge rather than within the cluster. Installation is done via Helm using an Ngrok API key and AuthToken, after which a sample app can be deployed and exposed through a standard Kubernetes Ingress resource tied to a static Ngrok domain. The setup also supports securing applications with GitHub OAuth and other authentication methods such as OpenID Connect and SAML, all enforced before traffic reaches the cluster. The result is a publicly accessible Kubernetes application reachable through a static Ngrok domain with minimal internal networking changes.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer Documents Journey Into LFX Mentorship Working on Post-Quantum Cryptography Tool

A developer has shared their experience of being selected for the Linux Foundation's LFX Mentorship Program to work on CBOMKit, a project tied to post-quantum cryptography. The mentee, guided by mentor Aditya Koranga, began the program with limited knowledge of OpenSSL and has since learned that it comprises four distinct components: libcrypto, libssl, a command-line tool, and the EVP API. Through the mentorship, they discovered that OpenSSL underpins widely used software including Nginx, PostgreSQL, and JWT libraries, often invisibly handling encryption tasks. The developer also explored how BoringSSL emerged as a Google fork following the 2014 Heartbleed vulnerability, and how Node.js now supports post-quantum algorithms natively via OpenSSL 3.5. The post reflects both the technical progress made and the gaps in understanding that remain as the mentorship continues.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Deploy PocketBase Open-Source Backend on Linux with Docker and HTTPS

PocketBase is an open-source Go-based backend that packages a real-time SQLite database, authentication, file storage, and an admin dashboard into a single binary. A deployment guide published on DEV Community walks developers through setting up PocketBase on a Linux server using Docker Compose, with Traefik managing automatic HTTPS via Let's Encrypt. Admin credentials are securely passed through environment variables, and the setup exposes PocketBase at a custom domain. The guide also demonstrates creating a sample collection called 'tasks' and querying it through PocketBase's REST API using curl. The tutorial is aimed at developers seeking a lightweight, self-hosted backend solution without complex infrastructure.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Differential Testing Exposes Silent PACE-to-BAC Fallback in Open-Source eMRTD Libraries

Researchers tested two widely used open-source e-passport reader libraries — gmrtd (Go) and JMRTD (Java) — by replaying identical synthetic protocol traffic against both, without any physical passport or NFC hardware. The experiment simulated a scenario where the newer PACE authentication protocol fails and the system silently falls back to the older BAC method. Both libraries completed the session successfully via BAC after PACE returned an error code, but neither surfaced an explicit indication to the application that a protocol downgrade had occurred. The findings highlight a gap that standard conformance testing misses: two libraries can behave identically in observable output while leaving applications unaware of a security-relevant negotiation failure.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Self-Host Neko Virtual Browser on Linux Using Docker and Traefik

Neko is an open-source platform that runs a virtual browser inside Docker and streams the session to multiple users simultaneously via WebRTC with synchronized audio and video. The setup uses Docker Compose with Traefik as a reverse proxy to handle automatic HTTPS certificate provisioning through Let's Encrypt. Firefox profile data is stored persistently on the host, and shared memory is set to 2GB to prevent rendering crashes. Admins can control input handoff between connected users, while participants join using a separate user password via a web interface. UDP ports in the 52000–52100 range must be open for WebRTC media traffic to flow correctly.

0 comments Read more at DEV Community