August 2024 Summaries

Semaphore will remove the Xcode 14 image from their machine pool on October 1, 2024, affecting Apple developers who use Xcode 14 for their projects. This change aligns with Apple's requirement that, by April 2024, all iOS and iPadOS apps submitted to the App Store must be built using at least Xcode 15 and the iOS 17 SDK. Organizations using the Xcode 14 image can determine their impact by checking their project settings via the Workflow Editor or searching for "macos-xcode14" in their pipeline YAML files. To prepare, affected organizations are advised to switch to the Xcode 15 image before the deprecation date, updating their macOS image settings accordingly and thoroughly testing workflows with the new image. Support is available for any questions or assistance needed, and developers can discuss this topic further on Semaphore's Discord channel.

Ingress controllers have traditionally managed client traffic to applications in Kubernetes clusters using the Ingress API, which, despite its utility, has limitations such as its terse design and lack of extensibility. Recognizing these shortcomings, the Kubernetes community developed the Gateway API, which achieved General Availability (GA) status in October 2023, to offer a more robust solution for traffic management. The Gateway API introduces several enhancements over the Ingress API, including a role-based system with multiple object types like GatewayClass, Gateway, and HTTPRoute, and support for multiple networking protocols beyond just HTTP. It also provides expanded traffic management features such as traffic splitting and request modifications, alongside a more formal method of extension through policy attachments. The tutorial detailed in the text guides users through configuring ingress traffic to an example application in a local Kubernetes cluster using the Gateway API, employing a local development cluster set up with the Kind tool and the Envoy Gateway implementation. This process involves deploying an application, installing and configuring the Envoy Gateway, creating a GatewayClass and Gateway, defining an HTTPRoute, and finally using a web browser to access the application, demonstrating the Gateway API's capabilities and improvements over the Ingress API.