Replicated Runthrough: Outdated 101

Greetings and welcome back for the next episode of the Replicated Runthrough series. This time we’re going to discuss Outdated.sh, an open source kubectl plugin that finds and reports outdated cluster images. The Technical Explanation Outdated repeatedly queries readable pods in all readable namespaces, looking for the podspec of container images and any init container

Replicated Runthrough: Troubleshoot 101

Greetings and welcome to part two of the Replicated Runthrough series. We’ll will be covering Troubleshoot.sh, a Kubernetes plugin for – you guessed it – troubleshooting host and cluster-level issues. Part of a suite of Kubernetes cluster maintenance tools by Replicated including (but not limited to) Outdated, Unfork, and KOTS, Troubleshoot is a highly customizable,

Replicated Runthrough: kURL 101

TL;DR – kURL deploys entire Kubernetes clusters, pre-configured with as many or as few add-ons as your organization needs, delivered via the cURL utility. Greetings and welcome to our new Replicated Runthrough series, where we teach you about each project in the Replicated catalog in simple terms. Our first lesson will be on kURL, an

Build applications with Kubernetes, deliver to enterprise customers with Replicated

Docker containers and Kubernetes have already changed the way that applications are packaged and developed, but that’s only a part of their total promise. The driving principle behind Replicated is that they will also change the way enterprises consume applications—by eliminating the false choice between antiquated, complex on-prem software and modern, scalable, simple-to-manage software as

Replicated Studio: Develop faster, release more often.

We are excited to announce Replicated Studio, an isolated development environment which gives you and your team a faster way to build and iterate on your application releases. Over the last few months, we’ve been working to improve the development workflow. We recently released the Replicated CLI, which helps with automating Release creation and promotion

Automating your releases

Developers and teams are happiest when they release higher quality updates more often. And most importantly, so are your customers. Great tooling plays an important part in helping everyone reach this happy place. We are excited to announce the release of the Replicated Platform CLI. This touch of tooling helps teams iterate and release new

Replicated and Docker EE

Recently, Docker split their installation into two different packages: Community Edition and Enterprise Edition. The enterprise edition of Docker does not include any additional features, but rather it is built to run on operating systems that are designed for enterprise use. The community edition of Docker continues to run on free, open source, popular distributions

Even smaller Docker image sizes

In one of our recent posts, we looked at some of the core strategies for reducing a docker image size. Since then, new ways to reduce an image size have emerged, enabling even faster distribution of images and startup times. In this post, I’m going to set up a common scenario: a Dockerfile that builds

Replicated vendor portal updates

We’re excited to announce the release of a newly redesigned frontend for vendor.replicated.com. Over the past couple of years, we’ve been constantly updating the default, vanilla, bootstrap-powered version, but we decided to shake things up a bit and redesign it. But it’s a lot more than a simple redesign. We’ve added a lot of new

Replicated multi-channel licenses

All Replicated instances are installed with a single license file. The license file is connected to a release channel, and the installation will receive updates when a new release is promoted to that channel. This process has worked pretty well so far and continues to be the best option for most installations. But there are