July 2024 Summaries

MicroK8s is a lightweight Kubernetes distribution from Canonical that is optimized for low-resource environments and is particularly well-suited for edge computing, enabling efficient deployment and management of containerized applications on devices such as point-of-sale systems and controllers. It offers advanced features like GPU support and high availability configurations, making it capable of handling intensive workloads such as AI inference and data analytics while minimizing latency and enhancing security. ngrok, on the other hand, is a unified ingress platform that simplifies accessing workloads across diverse infrastructures, offering features like reverse proxy, API gateway, and global load balancing. By integrating ngrok with MicroK8s, users can address the challenges of edge computing, such as distributed infrastructure management, security, and data processing, by standardizing network access and ensuring compliance with security policies. This combination not only reduces the complexity and friction associated with deploying edge-based workloads but also provides secure, scalable access to applications and services, enhancing performance and reliability in edge environments.

Ngrok has introduced a significant update to its Dashboard, allowing users to customize timestamps by selecting their preferred timezone and date format, enhancing event clarity and debugging precision. This change addresses user feedback seeking easier alignment of timestamps with other tools, thus reducing misinterpretation of event occurrences. Accessible through the User Settings page, users can choose between local timezones or UTC and select formats such as month-day-year or day-month-year, with the flexibility to define custom options if needed. Additionally, the ngrok team has migrated issues from the original ngrok v1 repository to a new Community Feedback Github repository, encouraging user engagement and feedback. Another enhancement includes timestamp integration in the ngrok agent console UI to help distinguish between repeat requests, addressing a common user concern. These updates aim to improve user experience and foster community interaction.

Successful organizations rely on various software applications such as ERP, CRM, and payroll systems, which need to communicate with each other across multiple environments, making integration a complex task. E-commerce and development teams often require seamless data synchronization between applications like CRM, accounting software, inventory management, and CI/CD pipelines, but manual processes can be time-consuming and error-prone. Low-code automation solutions and Integration Platform as a Service (iPaaS) providers like Retool, UiPath, and Zapier offer efficient alternatives with reusable components, replacing complex scripts with user-friendly interfaces and pre-built connectors for popular applications. However, accessing on-prem resources like Jira, GitLab, and PostgreSQL can be challenging without requiring changes to customer networks. Ngrok provides a solution by allowing connectivity to these resources without network modifications, using lightweight agents or SDKs, ensuring secure and efficient integration. With ngrok, businesses can automate workflows involving on-prem and cloud-based resources while handling security, performance, and high availability through its robust policy engine and global delivery network.

CEL Interpolation is a powerful capability that allows for dynamic configuration with ngrok's Traffic Policy Module by embedding variables and expressions in actions using the ${CEL} format. This enables more flexibility and adaptability in traffic policy configurations, enriching rules with connection, request, or response details through CEL variables and expressions. By leveraging CEL Interpolation, users can create custom responses or perform specific actions based on request data, such as adding dynamic headers to HTTP requests. The capability is supported only in specific policy action configuration fields and treats everything inside curly brackets as CEL expressions, including functions like split and join.

The text discusses the ongoing debate within the tech community about choosing the right cloud provider for SaaS hosting, highlighting the challenges and considerations involved in making such a decision. It explores the complexities of using hyperscalers, cheap VPSs, and even home labs, noting the associated costs, operational difficulties, and performance issues. Linode is presented as a cost-effective and developer-friendly alternative, with its reasonably priced compute VMs and global regions, gaining popularity particularly for applications requiring GPUs. The text introduces the concept of Global Server Load Balancing (GSLB) with ngrok as a solution to improve performance, availability, and resilience by routing traffic to the lowest-latency Points of Presence (PoPs) and supporting multi-cloud deployments. It emphasizes the benefits of using ngrok's GSLB, such as reduced complexity, solid security measures, and built-in observability, which are particularly advantageous for startups and SMBs lacking dedicated networking teams. The article concludes with an invitation to explore a step-by-step guide for integrating Linode and ngrok's GSLB, and to engage with the community for discussions and feedback.

The Kubernetes Gateway API has been extended with the addition of a new Traffic Policy Module, allowing users to manage traffic to their applications and APIs more easily. The module includes support for all traffic policy actions using a new Policy CRD, which is powered by ngrok's traffic policy engine. This allows users to create complex policies with minimal effort, using features such as custom responses, JWT validation, and more. The Gateway API also provides extension points that enable configuration in the same places where the rest of the configuration for a resource lives, making it easier to manage and understand. The new Traffic Policy Module is designed to simplify managing traffic to applications and APIs, and can be used with existing modules or ingress controllers.

Ngrok's Traffic Policy Module has been introduced to streamline configuration across various platforms, including cloud, API, SDKs, and Kubernetes. The module utilizes Common Expression Language (CEL) variables, which are designed for safety, performance, and ease of integration, to enhance policy evaluation, rule enforcement, and data transformation. Consistency in variable naming is emphasized to ensure uniformity across the Traffic Policy Engine, enabling users to create dynamic traffic filtering rules. CEL variables, which contain information from incoming connections like requests and responses, are crucial for adapting Traffic Policy rules to different conditions, thereby increasing document flexibility and responsiveness. Practical examples demonstrate how CEL variables, such as request method and content type, can be used to filter traffic effectively, offering users more control over their Traffic Policy documents. This functionality allows for better management of traffic to applications and APIs, promoting efficiency and effectiveness in traffic handling.