Application containerization has disrupted the way software applications have been built and deployed. Over the years, Kubernetes has stood out as one of the best platforms for container orchestration. It has helped many companies achieve scalability, resilience, portability, and better resource utilization in their products. However, managing Kubernetes is still complex. The first question which comes to mind is whether we should use a single cluster or a multi-cluster for Kubernetes.

One of the greatest challenges that operators and developers face is infrastructure provisioning: it should be resilient, reliable, reproducible and even audited. This is where Infrastructure as Code (IaC) comes in. In the last few years, we have seen many tools that tried to solve this problem, sometimes offered by the cloud providers (AWS CloudFormation) or vendor-agnostic solutions like Terraform and Pulumi.

The CircleCI visual config editor (VCE) is now generally available as an open source project. Development teams can now create and modify CircleCI config files in a visual drag-and-drop, low-code environment. The VCE is a node-graph editor that you can use to modify CircleCI config elements and generate config files. It provides a frictionless way to build CI/CD pipelines and interact with CircleCI’s platform in an efficient, user-friendly visual interface.

Kubernetes may provide an abundance of benefits, but those who are using it may be well aware that it often requires quite a bit (or even a lot!) of effort and skill to run the platform independently. So – rather than having to put up with it on their own, organizations are able to pay for a managed Kubernetes service instead. This is where Google Kubernetes Engine (GKE), Azure Kubernetes Service (AKS), and Amazon Elastic Kubernetes Service (EKS) come in.

In 2018, Honeycomb co-founder & CTO Charity Majors wrote a blog post titled, “An Engineer’s Bill of Rights (and Responsibilities).” We’ve recently updated and reposted it.

With the introduction of new application platforms like Kubernetes, oftentimes the DevOps tooling around it needs to evolve. Cloud Native technology is powerful but complex. This 5 minute demo video shows how Speedscale provides production simulation capabilities so you can check for resiliency, quality and scalability in your Kubernetes clusters. You can record data and traffic in production and replay sanitized traffic on the fly against a new cluster.

We are happy to announce that Charmed Kubeflow 1.6 is now available in Beta. Kubeflow has evolved into an end-to-end MLOps platform for optimised complex model training. We’re looking for data scientists, ML engineers and developers to take the Beta release for a drive and share their feedback! Read on to learn more.

The current trend to move to Zero Trust security architectures using the mantra “Never Trust, Always Verify” is a move that Teneo has long supported. The simple fact is that the traditional castle and moat approach to security built on VPNs is not fit for purpose in the modern world with hybrid users and infrastructures.

To avoid application downtime and data loss during Kubernetes clusters outage, platform and application operators need to utilize backups for recovery. These backups should contain both the application’s persistent data alongside its configurations, which can be restored to the same or different cluster to get back into production more quickly.

Ocean for Apache Spark has featured support for integration with Jupyter notebooks for quite some time – for details, please see our documentation. However, many developers would like to have this interactive notebook within their familiar IDE, such as VS Code, so that they can benefit from other IDE built-in features including Git integration. This article describes how to use VS Code to run Jupyter notebooks, while the code executes on an Ocean for Apache Spark cluster.