Open-sourced by Google in 2014, Kubernetes is a container orchestrator. That means it enables users to deploy and manage apps distributed and deployed in containers. It takes care of scaling, self-healing, load-balancing, rolling updates, etc. The project is managed by the Cloud Native Computing Foundation (CNCF) along with multiple other open source projects, and you can find it here on GitHub.

The cloud native stack, also referred to as the new stack, is composed of the new cloud-independent counterparts of cloud managed services. As enterprises moved to the cloud, they started leveraging cloud managed services such as AWS’ DynamoDB or GCP’s BigQuery. Very convenient, these on-demand services significantly increased developer productivity. Being proprietary, they only work on that specific cloud, however — a significant drawback.

Committed to providing reliable and secure Kubernetes across the enterprise, Kublr 1.14. brings further improvements to the UI, operations functionalities, and introduces support for SUSE Linux Enterprise Server.

While multi-site Kubernetes orchestration has numerous benefits, all of which have the potential to translate into a significant competitive edge, it still largely remains elusive — at least in the vendor space. The reason? Well, multi-site configuration is hard and, since during the first adoption wave, the focus was mainly on one cloud (most enterprises start with simple projects), there wasn’t a real need for it.

Since Google open sourced Kubernetes in 2014, it has become one of the most popular open source projects. Adopted by all major cloud providers, Kubernetes has undoubtedly become the de facto container orchestrator. But what is Kubernetes and container orchestration really about? Without the technical background and knowledge about the technology developments that preceded it, it can be challenging to wrap your head around it.

Almost every Kubernetes tutorial speaks about how to quickly deploy a container in a pod and expose it as a service. Mostly these tutorials focus on stateless services and ignore a deeper explanation of state management in Kubernetes. But Kubernetes supports both types of deployments, the stateless deployments and stateful deployments and they have somewhat different operational requirements.

This is the first in a series of tutorials on setting up a secure production-grade CI/CD pipeline. We’ll use Kublr to manage our Kubernetes cluster, Jenkins, Nexus, and your cloud provider of choice or a co-located provider with bare metal servers. A common goal of SRE and DevOps practitioners is to enable development and QA teams. We developed a list of tools and best practices that will allow them to iterate quickly, get instant feedback on their builds and failures, and experiment.