May 2020 Summaries

Multi-cloud organizations are increasingly common in enterprise computing, and utilizing an API-first strategy with a microservice-based architecture can expedite market delivery across diverse cloud environments. Essential to this approach are container orchestration and a solid CI/CD strategy. The article provides a guide for creating an automated workflow to deploy microservices and configure an API gateway using Kong Gateway within Kubernetes, managed through GitHub Actions. It requires pre-existing Kubernetes clusters, a Docker Hub account, and Helm for package management. The process involves setting up a GitHub repository, adding Docker credentials, and configuring a self-hosted GitHub Action runner. Deployment scripts are modified using JavaScript actions, and the workflow, when triggered by code changes, logs into Docker Hub, builds and pushes Docker images, and deploys services to Kubernetes. The guide also includes securing the upstream service through authentication adjustments in Kong and encourages modifications to the service code, which are automatically built and deployed via GitHub Actions. While the exercise is not a comprehensive CI/CD solution, it serves as a foundational step for developing more sophisticated workflows.

Kuma 0.5 has been released, introducing approximately 30 new features and enhancements, including support for multiple mTLS backends with automatic certificate rotation and a revamped GUI with improved scalability and usability. The update is available in both Kubernetes and Universal modes, and the project has adopted a new logo reflecting its maturity and increasing adoption in sectors like technology, finance, and telecommunications. Notable improvements include updated support for the latest Kubernetes and Envoy versions, official compatibility with OpenShift and Amazon Linux, and the introduction of Homebrew support for easier installation. The release emphasizes community engagement, highlighting contributors like Tharun, and encourages participation through community channels and GitHub. Additionally, users are advised to consult the Upgrade Guide for important changes introduced in this version.