No, I'm not talking about 'OpenAI', though you certainly can use it to assist in your API designs. I'm talking about the OpenAPI standard, a modern spec for defining REST APIs. If you're reading this, I probably don't need to tell you that REST APIs are ubiquitous in tech. Practically every company has at least one, whether it be an internal or customer facing API. While other types of APIs have been gaining traction the last few years (GraphQL, gRPC, etc), REST is here to stay.

Earlier this year, Mark Boost and Dinesh Majrekar had the chance to sit down with Solomon Hykes at Navigate North America 2024 to speak about his thoughts on the future of tech. Solomon is best known as the Founder, former Chief Technology Officer, and Chief Architect of Docker, and is currently the founder of Dagger, a programmable CI/CD engine that runs pipelines in containers, allowing development in various programming languages and execution across diverse environments.

Kubernetes troubleshooting is a critical skill for developers and system administrators managing containerized applications. It involves diagnosing and resolving issues within a Kubernetes cluster, ensuring that applications run smoothly and efficiently. Troubleshooting can range from simple configuration errors to complex networking issues, requiring a deep understanding of Kubernetes architecture and components.

In the world of Kubernetes, scale-down operations are crucial for optimizing resource usage and reducing costs. The scale-down process involves identifying underutilized nodes and efficiently bin-packing the pods to minimize the number of nodes required.

Test automation has become an indispensable part of software development, ensuring faster releases, higher quality, and overall cost-effectiveness. However, to reap the full benefits, it’s crucial to implement best practices that maximize efficiency and effectiveness. In this blog post, we’ll delve into some key strategies and tips for achieving optimal results with test automation.

As application platforms grow larger, the idea of DevOps teams where developers support the software development lifecycle, but also manage infrastructure and the platform, is beginning to reach the limits of what these teams can support. Rather than taking their best application developers and making them work on infrastructure problems, more organizations are coming to the conclusion that a centralized platform team specialized in that area is a better use of their developers’ skill sets.

Ephemeral environments are temporary, isolated, but self-contained deployment environments crucial for development and testing within software projects. While I already discussed the basics and benefits of Ephemeral Environments, today I will go through the practical steps of implementing ephemeral environments in your CI/CD pipeline using Kubernetes. I will start with how you can do it with Kubernetes native tools, and how you can automate the ephemeral environments in your CI/CD.

DevOps principles encompass a set of guiding philosophies and practices aimed at fostering collaboration and integration between software development and IT operations teams. These principles emphasize automation, continuous integration, continuous delivery, and a culture of shared responsibility.

At Cycle, we've taken a distinctive approach to VPN services, integrating them at the environment level of our platform. In a landscape where complexity can escalate quickly, anchoring each VPN to an environment–a VPC spanning the nodes of a cluster– simplifies management and maintains a high level of isolation.

Kubernetes 1.30, the latest release from the Kubernetes project, introduces several significant updates that enhance the orchestration capabilities of the platform. This release continues the trend of evolving Kubernetes into a more robust, scalable, and secure system for managing containerized applications across diverse environments. Below, we delve into the key updates in Kubernetes 1.30.