Ask Sendai

Less than a year ago, we started building Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes. The project has been growing in popularity, with many developers and DevOps engineers adopting it. A huge thanks to our awesome community of contributors and users! Today, we are excited to announce Argo Rollouts a new, Kubernetes-native, open source project brought to you by the Argo community and Intuit to provide missing deployment strategies like Blue/Green and Canary in a Kubernetes native and GitOps friendly manner.

Configuration management is a hard, unsolved problem. We share some unique insights about the strengths and weaknesses of several popular K8s config management tools. Of all the problems we have confronted, the ones over which the most brainpower, ink, and code have been spilled are related to managing configurations. — Brendan Burns, Brian Grant, David Oppenheimer, Eric Brewer, and John Wilkes, Google Inc. Configuration management is a hard, unsolved problem.

Implementing Continuous Delivery[1] at enterprise scale is a major challenge. As every company has to innovate their software delivery methods, we need to allow individual teams to learn and improve their own delivery pipeline. This is especially true in the Cloud Native world, where many best practices are still emerging. However, giving teams flexibility to experiment needs to be balanced with security and compliance requirements. In this post, I will explore how we successfully employed the GitOps architecture pattern to find a good balance between flexibility and security at a large enterprise customer of Container Solutions.

Booking.com is proud to announce the first public release of Shipper, an open source project that provides powerful, customizable rollouts to one or manyKubernetes clusters. Shipper uses Helm charts and native Kubernetes concepts to make it easy for anyone to set up blue/green or canary rollouts for their applications. The current release uses vanilla Kubernetes traffic shifting, so you don’t need a service mesh provider to get started. We intend to add support for other traffic shifting backends like Istio in the coming months.

Today we’re announcing official support for Kubernetes. While many organizations have already been combining Drone and Kubernetes for their deployments, today we’re delivering a native integration for a better user experience. Now your CI/CD Pipelines are translated into native Pods, Secrets, and Services. We’ve been at the forefront of the containerization movement; we started support for Linux containers, and when Docker came around we fully embraced their container runtime. Since then we’ve seen the hyper growth of Kubernetes platforms and users like eBay, Reddit and The New York Times adopting Drone and Kubernetes together.

Kohsuke Kawaguchi, creator of Jenkins and CTO at CloudBees, spoke last month at Jenkins World in Nice about five on-going initiatives to modernize the popular CI/CD tool. The initiatives revolve around Jenkins Evergreen, Jenkins Pipeline (Blue Ocean), Jenkins Configuration-as-Code, Jenkins X, and Cloud-Native Jenkins. While open source development is not going to disappear, the future of commercial open source is not very promising. Cloud providers are adopting open source software without necessarily adding value, or supporting future development.

The cost of managing microservices and the dependencies between them increase exponentially as their numbers rise. But things don’t have to be complicated. By making it easier than ever to add powerful new microservices, Kubernetes has become a driving force behind companies breaking up monolith apps and transforming them into microservice architectures. But as their numbers grow, the cost of managing microservices and the dependencies between them increase exponentially as well.

Doing Continuous Integration is a lot easier if you have the right tools. In our project at a german car manufacturer, we were tasked with developing new services and bringing them to the cloud. We had a centralized Jenkins instance, shared by all the teams in the department. It didn’t fit our needs and made it harder for us to deliver software quickly and reliably. Source: thoughtworks.com

Jenkins X is an open source system that offers software developers continuous integration, automated testing, and continuous delivery, known as CI/CD, in Kubernetes. Jenkins X-managed projects get a complete CI/CD process with a Jenkins pipeline that builds and packages project code for deployment to Kubernetes and access to pipelines for promoting projects to staging and production environments. Source: opensource.com